I'm actually working on a better caching strategy myself. I'm fairly new to Shindig though, and I'm still 'learning the ropes' so to speak. If I make any headway I'll definitely let you know. I'm certainly leaning towards ehcache though, as opposed to memcache.
On Wed, Jun 4, 2008 at 11:37 AM, Marijn Speelman <[EMAIL PROTECTED]> wrote: > Hi, > > I've got a couple of questions related to gadget caching in Shindig (Java). > > - Caching of rendered gadgets > I've been looking through the code and as far as I can see only the > Gadget specs (external XML files) are cached, in memory. Is this > observation correct? If so, wouldn't it make sense, performance wise, to > cache the rendered gadgets as well? I have no data on the performance of > the Gadget rendering (XML -> HTML+JS), but it would probably be best to > cache as close to the presentation of the gadget as possible. > > - Distributed cache > We're going to run Shindig on multiple (10+) servers to share the load. > At the moment Shindig only caches per instance on each server, so for > these kind of distributed setups it would be nice to have a distributed > caching system buldin. I'm planning to implement a Memcached backend for > this (because we already have a large memcached pool), but I was > wondering if anyone else is already doing the same or working on > something similar. I'm also curious about the progress on these two > tickets: > * https://issues.apache.org/jira/browse/SHINDIG-173 > * https://issues.apache.org/jira/browse/SHINDIG-279 (although this is > related to an ehcache implementation, it could be useful). > > Thanks in advance, > > Marijn Speelman > >
