Subject: Grouper Users - Open Discussion List
- From: Kathryn Huxtable <>
- To: Tom Barton <>
- Cc: Grouper Users <>, Dave Donnelly <>
- Subject: Re: [grouper-users] Ldappc performance
- Date: Mon, 12 Feb 2007 16:20:32 -0600
Well, you'll want to do something about LDAP injection in the
On 2/12/07 4:19 PM, "Tom Barton"
> Thanks Kathryn. I'm also CCing Dave Donnelly (signet developer), who is
> collecting issues with the Subject API and reference implementation that
> might be addressed in a future 1.0 release.
> Kathryn Huxtable wrote:
>> It looks like a lot of the culprit is the subject API. We use a JDBC
>> connector. The JDBCSourceAdapter class in subject 0.2.1 does not use
>> prepared statement handles. I get the following for a group with 13,357
>> Lookup time: 142327
>> Finder time: 50181
>> Using prepared statements I get:
>> Lookup time: 26550
>> Finder time: 53345
>> The times are in milliseconds. The lookup time is the total time required
>> for the member.getSubject() calls to complete and the finder time is the
>> total time for all the Provisioner.findSubjectDn(...) calls to complete.
>> These calls are in GroupEntrySynchronizer.storeGroupData.
>> Obviously, I can speed up the Provisioner.findSubjectDn call by cheating
>> using knowledge of how DNs are constructed from our IdMS, but you probably
>> ought to think about using prepared statements.
>> Prepared statements also eliminate problems with SQL injection.
- Ldappc performance, Kathryn Huxtable, 02/12/2007
Archive powered by MHonArc 2.6.16.