Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Severe performance issues with group-aware Roster

Description

The new group-aware Roster code generates a very large number of queries when displaying a Roster for a site in which there is a non-trivial number of groups.

Test scenario:

  • 1000 users in a site

  • 25 groups, 40 users per group

  • Select Roster tool (new profiles are created for each user)

  • Reset Roster tool

The page load time ranges from 90s to > 3min with production data. mysql logs show that the operation of resetting the tool generates 2 queries to SAKAI_PERSON_T, and over 130,000 queries involving SAKAI_REALM.

Trunk build, 21451.

Scripts used for generating test data are at:

http://source.cet.uct.ac.za/svn/sakai/trunk/scripts/loadtest/SakaiQA.jws
http://source.cet.uct.ac.za/svn/sakai/trunk/scripts/loadtest/roster_test.php (requires nusoap library)

Attachments

1

Activity

Stephen Marquard January 4, 2008 at 12:01 PM

Verified that performance in 2-5-x is acceptable in sites with a large number of participants (965) and groups (70+).

Not tested on 2-4-x; if that version of Roster (different code to 2.5 Roster) still shows performance issues, a separate JIRA should be opened.

Michelle Wagner September 6, 2007 at 6:36 AM

r34733

Michelle Wagner September 5, 2007 at 7:37 AM

We have a performance fix for 2.4 that will improve performance. Will merge into 2-4-x.

Stephen Marquard August 15, 2007 at 1:48 AM

The current trunk Roster destined to be in 2.5 doesn't have the same issues, so this is probably still a 2.4 issue but won't be a 2.5 issue.

Ryan Lowe August 14, 2007 at 12:29 PM

We have implemented all of the suggestions. From my understanding, Roster is getting a complete overall for 2.5.

Resolving JIRA

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Created February 15, 2007 at 6:25 AM
Updated June 23, 2014 at 9:28 AM
Resolved September 6, 2007 at 6:36 AM