800ms does sound excessive. Hobo+Rails is not the speediest beast in
the world, but it's generally not that slow in production mode The
first two steps for Hobo optimization are the same as for any Rails app:
enable production mode and to optimize database access. But it sounds
like you've already taken these two steps. Sometimes caching is easy
to add, and sometimes it isn't. The cookbook is a good example of some
simple caching. Another possible step is to switch to JRuby or Ruby
1.9, although that doesn't address the root problem and at best only
halve your response tim.
sorry I couldn't be more help,
Bryan
MartOn wrote:
Hello
I have a rather simple page of hosts (64 hosts in the database now).
If I show only 3 attributes in a table-plus it takes over 300ms to
render in production mode.
If I add additional 2 more nested attributes and also enable some edit
controls the page takes over 800ms to load.
(this is not the initial load, that takes around 3seconds).
NOTE! My DB: is 40ms
Has there been done profiling and optimization on Hoboć„€ view
rendering?
How can I improve rendering time?
In my mind the rendering should be at least 10times faster than it is
now :-)
Tests are done on a 2.4Ghz core2 Mac Book
/MartOn
--
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.
