[sakai2-tcc] Site caching

[csev]

This code is extremely fragile.  My recommendation is a complete rewrite - I even wrote myself a JIRA many years ago to that effect:

https://jira.sakaiproject.org/browse/KNL-89

If you recall, over the years, every time someone touches this code, it breaks badly - it would seem as though SAK-11440 is similar to all other attempts to tune Site Caching.

My plan in KNL-89 was to first remove *all* caching from Site and then test it thoroughly - and then make a nice, clean layer that should cache it nicely, touching the code at exactly one cut point and making very sure that invalidation was 100% perfect - and now of course - memory cleanup is perfect as well.

As more and more tools use properties for their primary storage - properties will become an increasing problem if not dealt with properly.

I fear that this is not something easily slid into 2.8 as a "quick fix" - the last thing we need is 2.8 shipping completely broken because of an unknown problem.     I would suggest that this needs a month of a person 100% dedicated to the problem - and we neither have the month nor the person.   So I also suggest that we *do not touch it at this time* and make this part of 2.9.

/Chuck

On Feb 16, 2011, at 8:10 PM, Matthew Jones wrote:

> This has probably been a problem for Sakai since ehcache was implemented in 2.5 (SAK-11440). This is not something someone would notice unless they had a high usage site, didn't restart often AND were looking at the heap dumps in a memory analyzer.
> 
> On Wed, Feb 16, 2011 at 2:04 PM, David Haines <dlhaines at umich.edu> wrote:
> It is not new to 2.8, we found it in 2.7.1.
> 
> - Dave
> 
> David Haines
> CTools Developer
> Digital Media Commons
> University of Michigan 
> dlhaines at umich.edu
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110217/00ceb461/attachment.html