Subject: Grouper Users - Open Discussion List
- From: Philip Harle <>
- To: "" <>
- Subject: [grouper-users] RE: PSP speed issues
- Date: Thu, 8 Sep 2016 15:39:15 +0000
- Accept-language: en-GB, en-US
- Authentication-results: spf=none (sender IP is ) ;
- Ironport-phdr: 9a23:4YbahxAgmuY60zcuah5TUyQJP3N1i/DPJgcQr6AfoPdwSP77rsbcNUDSrc9gkEXOFd2Crakb26yL6Ou5BCQp2tWojjMrSNR0TRgLiMEbzUQLIfWuLgnFFsPsdDEwB89YVVVorDmROElRH9viNRWJ+iXhpW1aJhKqfwVvIfntF5SXkt+6zfua+pvPbh9OiSbnJ75+MV/++QrLsdQOjJEnN7080ADho31Udv5QyH8yY1+fgkCvyN23+ctb8yVUuupp18daVaiyK7w4TLhZFHImOnox6eXtuAbIRBCT4nZaW25QjxkeUFuN1w3zQpqk6niyjeF6wiTPZcA=
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Just as a follow up to this, as mentioned previously we only publish a subset
of our Grouper groups to Active Directory. This is configured in
ldap.properties to only publish groups in the 'Applications' stem:
# The base Grouper stem to be provisioned.
However, in grouper_error.log I can see that the PSP is working its way
through all groups regardless of which stem they're located in. Groups in the
'Applications' stem do take a second or so longer than the others to process.
Is it correct that the PSP operates in this manner, or can it be configured
to ignore those groups that ultimately it won't be publishing to the Active
Being able to filter out unnecessary PSP enumeration is likely to give us a
significant improvement in processing time.
> -----Original Message-----
> From: Philip Harle
> Sent: 06 September 2016 14:02
> Subject: PSP speed issues
> Last year we migrated (via a fresh install) our instance of Grouper to
> 2.2.2. Since then we have experienced a significant degradation around the
> speed of provisioning with the PSP. We've been using the PSP to
> incrementally provision groups since the upgrade, and accepted the reduced
> However, as we've recently loaded all student data for our new academic
> year into Grouper, the PSP has been working through over a quarter of a
> million changes. This is taking between 1 and 4 seconds for each change, and
> we're estimating that this could take anywhere up to 2 weeks to work
> through all the changes. The server itself isn't stressed and is showing low
> CPU and RAM usage. I've attached a small snippet of the grouper_error.log
> showing the groups currently being provisioned. Some of these are being
> published to our Active Directory, others are Grouper-only.
> We're aware of performance issues with the PSP and the advice to upgrade
> to PSPNG in 2.3, unfortunately this isn't feasible for us at the moment.
> Hence, are there any configuration settings we should investigate/change in
> an effort to give some improved performance with the current PSP in the
> Phil Harle
> IT Service
> Newcastle University
- [grouper-users] RE: PSP speed issues, Philip Harle, 09/08/2016
Archive powered by MHonArc 2.6.19.