Child pages
  • Scalability and performance watchlist

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

This page is for Sakai issues arising from technical or architecture design decisions that impact negatively on scaleability or performance.

Slow tools

Forums

Mostly resolved in 2.5, though still shows slow performance for:

  • very large topics (say 500+ messages)
  • synoptic tool in my workspace
  • sites with a large number of groups
    Jira
    SAK-11798
    SAK-11798

Messages

  • Scalability issues sending messages in sites with large membership
    Jira
    SAK-14626
    SAK-14626
    ,
    Jira
    SAK-14392
    SAK-14392

Assignments

(resolved in 2.5)

Resources / Content Hosting

(improved in 2.5)

Gradebook

(mostly resolved in 2.5?)

Email Archive

(resolved in 2-5-x)

Tools / services which affect app server stability and performance

JSF "stuck threads" issue:

  • Tests and Quizzes:
    Jira
    SAK-11098
    SAK-11098

SQL Optimization

Table and index structure

Slow DB queries

  • Jira
    SAK-10193
    SAK-10193
    : Permissions checks slow in sites with large membership

Volume of database queries

  • Jira
    SAK-9862
    SAK-9862
    : Excessive db queries generated from permissions updates in sites with provided users.
  • Jira
    SAK-10859
    SAK-10859
    : Reduce number of CM queries required when user logs in (hibernate impl)

Completed issues

  • Jira
    SAK-8932
    SAK-8932
    : Chat "stuck threads"
  • Jira
    SAK-11636
    SAK-11636
    : HTTP Basic operations create a login event for each request and refreshes authzgroups
  • Jira
    SAK-9860
    SAK-9860
    : Excessive db queries generated from Site Info / user service. Site Info generates 5 db queries for every site member (1 to SAKAI_USER and 4 to SAKAI_USER_ID_MAP).
  • Jira
    SAK-9887
    SAK-9887
    : Excessive db queries for dropbox on site update actions
  • Jira
    SAK-10021
    SAK-10021
    : Dropbox Performance Problems
  • Jira
    SAK-8780
    SAK-8780
    : The table structure of SAKAI_SESSION forces the db (at least mysql) to do a full table scan to find out which sessions are currently open.
  • Jira
    SAK-5943
    SAK-5943
    ,
    Jira
    SAK-11544
    SAK-11544
    : Performance degrades with a large number of messages
  • Jira
    SAK-13021
    SAK-13021
    : Section Info: Overview page generates too many queries leading to performance issues
  • Jira
    SAK-13312
    SAK-13312
    : Improve Group performance