What I've been doing is fragment caching cards that get called a lot so that reads are relatively cheap.
It takes it from 800ms in dev mode (no caching) to 57ms production on same box. If you don't have that many new items then page caching or fragment caching the content block will improve that even more. What I found, is the way dryml breaks everything down it becomes real easy to implement fragment caching particular to a specific model. On Feb 23, 2:51 pm, Tom Locke <[email protected]> wrote: > I know this is a bit of a half-hearted solution, but you could always > switch to good-old ERB for loops for the table. i.e. optimize where > your pain points are. > > Tom -- 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.
