Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] Update: Subject API Slowness

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] Update: Subject API Slowness

Chronological Thread 
  • From: Tom Barton <>
  • To:
  • Subject: Re: [grouper-dev] Update: Subject API Slowness
  • Date: Tue, 03 Oct 2006 21:09:37 -0500

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.


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.

Archive powered by MHonArc 2.6.16.

Top of Page