Performance optimization by rethinking My staff and Organisational Units

1 Initial Problem

Staff view data (and OU in general) queries suffers from significant performance issues when running ILIAS installations with a large number of users and organizational units. The organization "IBB" runs an ILIAS 6 installation with ~10.000 users and a large number of organizational units. For some users the data query in "my staff" exceeds a processing time of 2 minutes or even leads to a timeout in some cases.

Qualitus discussed the problem with Michael Jansen and he already developed some solutions for IBB to partially improve the overall performance of the queries up to 50 %. However, the queries still are taking too much time (> 1min) and Michael concluded that it would be necessary to rethink the "my staff" structure for satisfying improvisation results. We will share the anaylses of Michael shortly.

Expected result should be that the queries in "my staff" will not exceed 5 seconds, even if installations have an above-average number of users and organizational units.

2 Conceptual Summary

Will be added shortly.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Tobias Pelster (pelster@qualitus.de)
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• IBB - Institut für Berufliche Bildung AG

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.