Grouper Developers Forum

[Tom Barton <>]

The grouper api uses ehcache, and there've been some additional optional 
caching capabilities introduced in HEAD since the 1.0 release. However, 
we haven't done thorough benchmarking, and what little there is 
indicates mixed results to overall performance depending on the backend 
database and query types.

Tom

Chad La Joie wrote:
> I'm in the same boat Chris is in, and I'll offer one other suggestion 
> that he didn't.
>
> Consider setting up a second level cache with Hibernate.  By default 
> Hibernate keeps a Hibernate session scoped cache so repeated queries 
> within that Hibernate session are pulled from cache first.  Unless you, 
> or the grouper folks, have specifically done other that session is 
> closed, at latest, at the end of each HTTP request.
>
> A second level hibernate cache keeps the information around between 
> requests.  Configuring it might save you a whole lot of those DB calls, 
> and should help even if the paging mechanism doesn't support Hibernates 
> paging API.  Here's some info on it.
>
> http://www.hibernate.org/hib_docs/v3/reference/en/html/performance.html#performance-cache