Grouper Developers Forum

[Chris Hyzer <>]

I added some configs for testing to delay one of the widgets:

 

# if you are testing the widgets, put a sleep there

# max widget millis must elapse before the JSP displays

uiV2.index.test.sleepIn.recentlyUsed.widgetMillis = 0

uiV2.index.test.sleepIn.myFavorites.widgetMillis = 0

uiV2.index.test.sleepIn.groupsImanage.widgetMillis = 0

uiV2.index.test.sleepIn.stemsImanage.widgetMillis = 0

uiV2.index.test.sleepIn.myMemberships.widgetMillis = 0

uiV2.index.test.sleepIn.myServices.widgetMillis = 0

 

So... if you have the timeout uiV2.index.widgetMaxQueryMillis = 5000, and you have a widget timeout set to 5500ms, and it is the first widget, then it will run for 5 seconds, give up, and go to the next widgets. but if the next widgets take 600ms, then by the time the JSP renders, the 5500ms will have finished and the widget will display.

 

Another scenario, if you set the widget millis to 6000, and the max is 5000, then the first one will run for 5 seconds, go to the next one, which runs for 5 seconds, then it goes to the last one, which runs for 5 seconds. The result will be the page takes 15 seconds to display, and the first two widgets will display and the last one wont.

 

https://github.com/Internet2/grouper/commit/68a7675558d754978d3972ca47832f2810b1834b

 

https://bugs.internet2.edu/jira/browse/GRP-1046

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Chris Hyzer
Sent: Saturday, October 04, 2014 11:44 AM
To:
Subject: [grouper-dev] slow widgets affects ui 2.2 splash page performance

 

Note, shilen tuned some queries on the main page, but the widgets can still be slow if the users has a lot of privileges.

 

If a widget takes longer than the configured amount, then just display the page with a link to refresh it. See screenshot.

 

https://bugs.internet2.edu/jira/browse/GRP-1046

 

https://github.com/Internet2/grouper/commit/4c8bf00c2c008ef8f988428a813ec46ab69bb66f

 

This is fixed in 2.2.1.

 

Configure this in grouper-ui.properties:

 

# number of millis that widget queries must complete in before they are abandoned and the user must click a link to display it

# -1 means dont run in threads, and just draw the screen no matter how long it takes. 0 means, dont even try to load the widgets,

# let the user do it themselves

uiV2.index.widgetMaxQueryMillis = 5000

 

Thanks,

Chris

 

See “Groups I Manage” below, it was slow, so you get a link you can use to see the widget…