GROUPER:  About   FAQ   Software  Documentation   Contribute   WG   Contact

Performance Issues - Next Steps

    Please notify the grouper-dev mailing listas you edit this page.  Thanks!


     C.f. grouper-dev email from Tom Barton, 26-Jul, subject: perf issues next steps, in the mail archives.
Below is the set of tasks rolled-up to each functional issue which they mitigate, updated based on the conference call yesterday (25-Jul-07). Also shown are the next steps and the person or group assigned to each. The other tasks are considered to be "on-deck". Please do acknowledge or amend this to ensure that I've got it right.

Thanks all for your help!
Tom


Notes and Next Steps

  1. GRP-7 depends on GRP-12 being completed.
  2. [blair] to work on GRP-12.
  3. [blair] to work on GRP-6.
  4. [blair] to work on GRP-10.
  5. [blair] to determine why listing a group's membership produces a separate SQL query for each membership.
  6. [Duke] to perform JNDISourceAdapter profiling or other diagnostics to identify specific perf issues.
  7. [Duke] to profile a group search to further identify where all the time is spent.
  8. [Duke] to continue their investigation into the "SQL batching" phenomenon and report their conclusions.

In addition, Duke finds the work-arounds pertaining to TAAdmins mentioned below to be reasonable for now, and will implement them at a convenient time.

Functional Issues and Associated Work Items

Browsing My Memberships or Manage Groups
a. [GRP-7] Add methods for finding child stems and groups where a Subject has the specified access or naming privileges
b. modify UI to take advantage of these
c. [GRP-10] Modify Membership indices based upon recommendations from Duke

Listing group members is slow
a. improve JNDISourceAdapter performance
b. [GRP-6] API Subject caching no longer caching everything that it should
c. [GRP-7] Add methods for finding child stems and groups where a Subject has the specified access or naming privileges

Ldappc performance
a. improve JNDISourceAdapter performance
b. [GRP-6] API Subject caching no longer caching everything that it should
c. [GRP-12] Poor integration with Ldappc: subordinate-stem-query causes a full table scan
d. [GRP-13] Poor integration with Ldappc: attribute-matching-queries causes a full table scan
e. [GRP-14] Poor integration with Ldappc: Null DTO error message causes Ldappc runs to fail
f. modify Ldappc to take advantage of these
g. modify Ldappc to cache more group data

Group search
a. [GRP-9] A number of methods for retrieving groups by attribute cause full table scans.  Document methods where this is the situation and provide alternates where possible.
b. modify UI to default to equality-matched & scoped searching

TAAdmins using Manage Groups
a. subclass PrepareMenuAction to omit Manage Groups for TAAdmins

Add member to TAAdmins takes hours
b. perform this inherently slow operation in a separate JVM, eg, by running a gsh script

XML import/export doesn't scale
a. improve JNDISourceAdapter performance
b. profile XMLReader and XMLImporter to see where time and space is
being spent

Variant Subject presentation depending on user and Subject's FERPA status

   (question) Questions? (info) Contact us.


GROUPER:  About   FAQ   Software  Documentation   Contribute   WG   Contact