On Monday, September 10, 2012 12:32:32 AM UTC+1, Ruby-Forum.com User wrote: > > Can anyone explain where are the milliseconds getting lost - > > Completed 200 OK in 438ms (Views: 145.0ms | ActiveRecord: 15.0ms) > > Completed 200 OK in 378ms (Views: 206.0ms | ActiveRecord: 2.0ms) > > Completed 200 OK in 275ms (Views: 62.0ms | ActiveRecord: 35.0ms) > > This is by far the most time consuming part of the entire request so I > am hoping to explore more. > > Views & ActiveRecord don't include time spent in the routing stack or in evaluating your controller or model code (other than then actual sql queries) or querying other datastores (mongo, elasticsearch, solr etc.)
Fred > -- > Posted via http://www.ruby-forum.com/. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/COpXbw3TmA8J. For more options, visit https://groups.google.com/groups/opt_out.
