Grouper Developers Forum

[Kathryn Huxtable <>]

Okay, I see that the problem is that it takes over 15 minutes to search the
existing subject DNs in my LDAP directory.

That does it. I'm rewriting this thing. It will probably end up only usable
at KU, but I'll still make it available.

-K


On 1/29/07 10:06 AM, "Kathryn Huxtable" 
<>
 wrote:

> I really need better performance out of ldappc. It takes 20 minutes to
> complete a polling cycle even when nothing changes. Using triggers on the
> database tables I can get data provisioned within a couple of minutes.
> 
> Is this because of the database reorganization in Grouper 1.1, which I have
> not implemented since I am already in production with Grouper 1.0, or, more
> likely, is it the incredibly large number of lazy fetches due to not using a
> join query in the Grouper API. (I've mentioned this before.)
> 
> I'm debating the merits of rewriting ldappc, at least in part. I have two
> motivations:
> 
> 1) Increase efficiency of the Grouper queries, and
> 2) Provision the data into my person registry rather than into LDAP. For me,
> LDAP is a secondary data repository and I should be able to provision almost
> all my data into multiple directories.
> 
> Anything I do will be posted back to the community, of course.
> 
> Ideas?
> 
> -K
>