Grouper Users - Open Discussion List

["Black, Carey M." <>]

Dusty,

                Did this start recently, or is it just something that “finally got bad enough to ask about”?

 

 

 

All,

 

FWIW: I don’t see any references to this setting in the Tier Deployment guide.

                I did find one ref on the Grouper WIKI: https://spaces.internet2.edu/display/Grouper/UNC+load+testing+grouper

                                This page appears to be about v1.6 vs v2.3 performance.

                                With different grouper data structures and apples to oranges deployment models.

                                So.. version changes, different data structures, and different deployment models…..

                                hum… had to know what details matters more than others. But a good read all the same.

 

 

Is there any guidance on when this setting should be seriously considered?

Can anyone identify the variables/factors that make this performance issue better/worst?

                ( my first thoughts of possibilities…)

                More Stems that are flat?

                More Stems that are bushy?

                Depth of Stems?

                Raw count of Stems(folders)?

                Total Number of groups?

                Dynamic characteristics like how much data/groups/permissions are being changed?

                CPU/RAM load on the server?

                Max RAM limit for tomcat?

                Number of groups on the user in the session?

 

                Is any of this computation cached for the user?

                When does it happen?

                                At login?

                                At page load?

                                Other?

 

 

 

And while we are talking about the “Browse folders” widget…

                Is there any way to get it to add/remove as the user adds/removes folders/groups? ( Focused only on their session of the UI. )

                                If not, is there a Jira request for that yet?

                                It seems like it should be possible…… _javascript_ anyone? :^)

 

--

Carey Matthew

 

From: [mailto:] On Behalf Of Edenfield, Dusty
Sent: Wednesday, September 27, 2017 2:02 PM
To: Redman, Chad <>; Gettes, Michael <>;
Subject: RE: [grouper-users] Browse folders section is slow to load

 

Changing that option to ‘false’ helped tremendously.

 

Thanks!

 

From: [] On Behalf Of Redman, Chad
Sent: Wednesday, September 27, 2017 11:45 AM
To: Gettes, Michael <>;
Subject: RE: [grouper-users] Browse folders section is slow to load

 

Correct, this can be bypassed with an option in grouper.properties:

 

# if folders should be shown only if there is an object inside that the user can see

security.show.folders.where.user.can.see.subobjects = false

 

 

This is available since API patch 15 (GRP-1320)

 

 

-Chad

 

 

From: [] On Behalf Of Gettes, Michael
Sent: Wednesday, September 27, 2017 11:29 AM
To:
Subject: Re: [grouper-users] Browse folders section is slow to load

 

+1 - recommendations to tweak config if appropriate is appreciated.

/mrg

 

On Sep 27, 2017, at 11:27 AM, Edenfield, Dusty <> wrote:

 

In the Grouper UI in 2.3, we’ve noticed that the folder tree is very slow to load for users that don’t have a lot of privileges.  For super users, the tree loads quickly.  Is this because it’s doing a view privilege check for each existing group to determine if it can be displayed in the tree browser?

 

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

Dusty Edenfield
Systems/IT Architect
OIT-Enterprise Information Systems
Georgia Institute of Technology
(w) 404-385-3945