Sakai Performance Issues

sakai_2-5-x

sakai_2-4-x

• From and email exchange with R. P. Aditya : aditya@grot.org

  • On Fri, Aug 31, 2007 at 11:50:34AM -0700, Thomas Amsler wrote:
    > > Are the 15 connections in the DBCP connection pool you max setting? I think 
    > > the default is max=50 in OOTB.
    
    on our 8 appservers, we use:
    
    minIdle@javax.sql.BaseDataSource=1
    maxIdle@javax.sql.BaseDataSource=14
    initialSize@javax.sql.BaseDataSource=15
    maxActive@javax.sql.BaseDataSource=14
    
    and in typical use, even at peak, we only see 2-3 active via Oracle
    
    The most important thing for Oracle is that maxIdle = maxActive so that the
    pool connections are never dropped or recycled since setting up new
    connections is terribly expensive...
    
    Adi
    

• SAK-9860 : Excessive db queries generated from Site Info / user service
  • From Ian:

    Just commited a fix agaisnt SAK-9860
    
    Its not a total fix, but you should be able to patch 2.4.x (once fully tested) and the profiler is saying the 
    number of queries for a since request is now 1 rather than 4 the first time per user and then 0 after that.
    
    Needs testing though, and only eliminates the EID/ID SQL.
    

• SAK-11279 : Spurious presence events
  • From Stephen:

    Hi all,
    
    If you're running 2.4.0 or 2-4-x in production with presence enabled, you will probably want to apply the fix to presence/courier from:
    
    http://jira.sakaiproject.org/jira/browse/SAK-11279
    
    This is a bug that logs 2 presence events every time a presence refresh is made (every 30s per user). Fixing this reduced the volume of presence events in our production system by a factor of 10 or more.
    
    Regards
    Stephen