Subject: Grouper Developers Forum
- From: Kathryn Huxtable <>
- To: Mark Weber <>, <>
- Subject: Re: [grouper-dev] Subject API Slowness
- Date: Fri, 29 Sep 2006 12:34:23 -0500
Me, I just bypassed the subject API and simulated subjects, querying my
subject source directly. It sped things up enormously. -K
On 9/29/06 11:51 AM, "Mark Weber"
> We've started doing some initial load testing and found that it's pretty
> slow. Our initial estimates put a full load of our population into
> grouper, via the xml-import facility, would take about 8 days.
> I think I've narrowed it down to the Subject API. Specifically the
> Subject API configured using JNDI/LDAP adapter. For Instance, the UI
> takes 74 seconds to load the " All Groups - Current subjects with
> [xyz] privilege" page. It displays the first 50 members and creates a
> connection, bind, search, result, unbind, and disconnect for each person
> on the page. Same with the xml-import.
> I noticed that on the import, for each subject, the API handles each
> request discretely (connect, bind, query disconnect) instead of in mass
> (connect, bind, query, query, query...unbind). And it's possible (and
> likely) that I just have it mis-configured. So, is there some
> configuration option that allows for connection pooling within the
> subject API when it's using LDAP?
> This is an assumption, but if we used the jdbc source adapter instead,
> would it use connection pooling and thereby eliminate the problem
- Subject API Slowness, Mark Weber, 09/29/2006
Archive powered by MHonArc 2.6.16.