Grouper Developers Forum

[Shilen Patel <>]

blair christensen. wrote:
> Gary: Could you clarify what API operations are being performed in the
> UI during some of issues? It might help clarify areas in most need of
> performance improvements.
>
> On 7/6/07, Shilen Patel 
> <>
>  wrote:
> > 1.  Navigating through the stems viewable in the "My Memberships"
> > section in the UI takes about 2-3 seconds per page.
> > 2.  If you are a member of the TAAdmins group, the "Manage Groups"
> > section takes about 10 minutes to load.
> > 3.  If you're not a member of the TAAdmins group and have no memberships
> > and no privileges, the "Manage Groups" section still takes about 30
> > seconds to load.
> > 4.  Performing a group search takes about 20-30 seconds even if no
> > results are returned.
> > 5.  Listing group members also takes a long time.  If a group has X
> > members and you want to see the first Y members, listing the group
> > members causes at least X database queries and 2Y LDAP queries.
> > 6.  Adding a member to the TAAdmins group takes hours.
>
> > 7.  The xml-import takes about 3-4 days for us and requires 4 GB of
> > memory allocated to the Java process.
>
> Wow.  How many groups/memberships are being added?

The import file is 230 MB (from the 1.1 Grouper export).  There are 
846,102 memberships, 102,093 groups, and 89,514 stems.

> > 8.  The only way to restrict FERPA protected data is to prevent users
> > from having read access to specific groups and stems that may have FERPA
> > protected data.  It would be nice if Grouper had a way of honoring FERPA
> > protected data in a way such that if a user has a FERPA flag set in
> > LDAP, people viewing members of the group would see something like
> > "Anonymous User" instead of the user's name.
>
> This is a restriction that you would like to have when displaying
> memberships in the Grouper UI?

Yes, it would be nice if that option was available when displaying, 
searching, exporting, etc FERPA protected data.

Thanks,

-- Shilen