On Jul 11, 2012, at 5:45 PM, Raphael Sofaer wrote: > Hi Hobo users, > > I'm a developer with rails experience working at a neuroscience lab, and we > have a legacy hobo app which is ridiculously slow. Some of our index pages > take 10 seconds to load. All the time is in view rendering, effectively none > in ActiveRecord. How can I figure out what's wrong here? Most of the places > I would but benchmarking functions are wrapped up in hobo methods, so I'm not > sure what to do. The slowest page uses hobo_index in the controller, and > collection and table_plus in the dryml file. Are those a recipe for > disaster? I don't think there's any page that has a sub-second load time, > though.
The first thing I'd check is the server - is it running in production mode? The behavior you've described sounds a lot like the result of an app running in development mode. Also check to see if the server is overloaded (swapping, etc) as some of the old defaults for gems like Passenger specified an unreasonable number of processes for small machines. Note that some of the timing stuff (especially on older Rails) will not always give sensible results; for instance, a default index action will only actually load records when they're used on the page, causing the view to get charged most of AR's time as well. Ping me off-list if you'd like another set of eyes on the code. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
