Grouper Users - Open Discussion List

[Jared Hoffman <>]

Wonderful, thank you! I can confirm similar levels of improvement with our data. 

For 1820 members, 320 seconds down to 4.5 seconds.

For 146 members, 26 seconds down to < 1 second.

I also tested this with the "run loader process to sync group" in the UI. The patch appears to only affect the scheduled cron tasks. I did configure the subjectIdentifierAttribute0 in the sources.xml for the UI and API.

On Fri, Oct 14, 2016 at 12:13 PM, Shilen Patel <> wrote:

I've added a new patch for 2.3 that significantly improves the performance of the loader in cases where you're using a subject identifier instead of subject id.   I did a simple test of re-running a loader job for a group with 2936 members where the loader job used subject identifier. Before it was taking 90-100 seconds. Now it takes less than 1 second.

It requires that you configure the sources.xml file to save the subject identifier into grouper's grouper_member table.  See https://bugs.internet2.edu/jira/browse/GRP-1381.

Thanks!

- Shilen

On 10/5/16, 12:16 PM, "Shilen Patel (JIRA)" <> wrote:

Shilen Patel created GRP-1381:

---------------------------------

             Summary: Use member table subject identifier in loader jobs to improve performance

                 Key: GRP-1381

                 URL: https://bugs.internet2.edu/jira/browse/GRP-1381

             Project: Grouper

          Issue Type: Bug

      Security Level: Standard (Standard bug, may impact functionality but does not represent a security vulnerability)

          Components: grouperLoader

            Reporter: Shilen Patel

            Assignee: Shilen Patel

             Fix For: 2.3.1, 2.3.0.patch

--

This message was sent by Atlassian JIRA

(v6.4.11#64026)

--

Jared Hoffman • Associate Director for Enterprise Infrastructure

Kenyon College LBIS •  • 740.427.5948