On Mon, Aug 27, 2012 at 4:28 PM, Reinier Balt <[email protected]> wrote: > Hi all, > > I've tried the new cache-digests gem to easy add caching to Tracks. > (I had to clone the gem to enable it running on ruby 1.8.7) >
Perhaps it would just be better to drop 1.8 support for master instead? I don't think we need the maintenance burden at this point. The majority of the ruby/rails community has also made the switch to 1.9 > I have cached Todo, Context (different for home page, tag page and tickler) > and Project. This brought nice speed improvements for server-rendering. > > For who is interested, it is currently on the add_cache branch if you want > to test it out. I've added bullet and rack-mini-profiler there too. The > second is enabled in development only so you can see the difference. Be sure > to enable caching in development in config/environments/development.rb if > you try this from development environment. Production has caching enabled by > default. > > Please note: The biggest culprit right now is the javascript performance. > This is not affected in any way by this caching > I'm a bit confused. If the biggest culprit is the javascript performance, shouldn't we be focusing on that? Or is javascript performance now the biggest culprit since you adding caching? > N.B. This message is cross-posted to the old and new mailing list. This list > will be closed shortly. The new list is at > https://groups.google.com/forum/?hl=en&fromgroups=#!forum/tracksapp > Please send out a separate announcement for this. This is too important to be buried here, IMO > Reinier _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
