Subject: Grouper Developers Forum
- From: Chris Hyzer <>
- Subject: Re: [grouper-dev] Manage Groups
- Date: Tue, 10 Jul 2007 22:48:31 -0400
I havent been in the grouper source code much, but I have done a lot of hibernate tuning, and 2000 queries jumps out as a red flag. Our DB queries take ~15 ms from java, and 2000 might take too long. When we see this it is usually the N+1 query problem, and generally, fixing it this means having hibernate batch the queries, outerjoin, cache global data, or do not map relationships and do this manually with other HQL or criteria queries... but again, sorry for not knowing the specifics, maybe this is not possible / feasible...
Michael R. Gettes wrote:
what does "top three" mean? Getting a breakdown of how the 7.9 secs are spent
would be very interesting. By time, by SQL statement (if all the same) and by
data transmitted (bandwidth). This type of profiling is really useful!
On Jul 10, 2007, at 19:06, Shilen Patel wrote:
Over 2000 SELECT statements were also executed that in total took 7.90 seconds. The top three queries in terms of execution time and invocation count are the following:
- Manage Groups, Shilen Patel, 07/10/2007
Archive powered by MHonArc 2.6.16.