Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] caching & ldappcng

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] caching & ldappcng


Chronological Thread 
  • From: Tom Zeller <>
  • To: Chris Hyzer <>
  • Cc: Grouper Dev <>
  • Subject: Re: [grouper-dev] caching & ldappcng
  • Date: Fri, 25 Mar 2011 09:26:18 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=MsENXuPwoL6cQ5hunOobHl+Rui3CCeQ30n3jg9sKezazM8SbvMaeZl5m3bMjUK/qaY ZmnX3JKFOvkMBcD4PwEGwQxbrg2amJU4ixG0RD46jqDdGCvKGTWQxanl3JG4Yy2MH6g3 bZdBoiEYwcytNAr1r4efaSsUcLk5Rk1+zIS94=

> Are you saying that if a cache config in the xml files doesn't exist that
> things should still work and it should just use the default cache config?  
> So that if people keep things as they are now, then everything will be the
> same.  But if they wipe out their xml files and just have a default config,
> that all caches will use those default config settings?

Yes, I think that <defaultCache /> should be the default for *all* caches.

And, there probably should be 1 xml cache config file.

No, if we change code, caches might not be the same (we will need to
check), unless <defaultCache /> always matches hardcoded defaults.

And, the cache config file(s) should include helpful text explaining
what that particular cache does :-)

And, perhaps the grouper daemon (or a scheduled job ?) should collect
hit and miss counts from all caches and store them in a table somehow,
with timestamps, to provide cache usage statistics. For example, after
running ldappcng, a deployer might like to know if they should
increase cache sizes for particular caches.



Archive powered by MHonArc 2.6.16.

Top of Page