[cle-release-team] [Building Sakai] 2.9.0 Realm/cache issue

[Aaron Zeckoski]

I agree with Matt Jones' comment that the best option here is to go
ahead and just flip these over to not overflow to the disk. For the
smaller and more core kernel caches this is probably better for
performance anyway. For larger caches (like User) this could be an
issue so I would not just do it to all of them.

-AZ


On Tue, Oct 16, 2012 at 9:49 AM, David Horwitz <david.horwitz at uct.ac.za> wrote:
> A heads up is I've discovered a similar case:
>
> https://jira.sakaiproject.org/browse/KNL-976
>
> D
>
> On 10/16/2012 02:44 PM, Adrian Fish wrote:
>
> I can well believe it. Where's the best place to set the prop? In
> authz-components.xml?
>
> On 16 October 2012 13:41, David Horwitz <david.horwitz at uct.ac.za> wrote:
>>
>> Yes that's right - if there are more than cacheMemory size items that are
>> younger than TTL and TTI than the least referenced one will be dropped. I
>> increased the size of the memory cache slightly.
>>
>> We've found that overflowing caches to disc can have worse effects that
>> going to the db anyway. Our site property cache did this and it saturated
>> disk IO
>>
>> D
>>
>> On 10/16/2012 02:28 PM, Adrian Fish wrote:
>>
>> There must be side effects to that though, surely? Does is just mean that
>> old stuff gets culled earlier?
>>
>> On 16 October 2012 13:15, David Horwitz <david.horwitz at uct.ac.za> wrote:
>>>
>>> Thanks to so pointers from Aaron it seems the simple solution is to set
>>> overFlow to disk to be false for that cache
>>>
>>>
>>> D
>>> On 16 October 2012 08:52, David Horwitz <david.horwitz at uct.ac.za> wrote:
>>>>
>>>> Jira'ed and having a look:
>>>>
>>>> https://jira.sakaiproject.org/browse/KNL-975
>>>>
>>>> D


-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile