Dashboard > SakaiPedia > Handling large site memberships
  SakaiPedia Log In | Signup View a printable version of the current page.  
  Handling large site memberships
Added by Ray Davis, last edited by Ray Davis on Feb 21, 2006  (view change)
Labels: 
(None)

The single most important step to take as of Sakai 2.1 is probably to enable user directory and security service caching. The legacy design tends to make many redundant small queries rather than a few pivotal top level queries. Make sure you have lines like this in your sakai.properties file:

# minutes to cache each user access in the UserDirectoryService - set to 0 to disable caching.
cacheMinutes@org.sakaiproject.service.legacy.user.UserDirectoryService=10
cacheCleanerMinutes@org.sakaiproject.service.legacy.user.UserDirectoryService=10

cacheMinutes@org.sakaiproject.service.legacy.security.SecurityService=5

Regarding scalability of the legacy authz design, see SAK-2660 - "Improve central management of role / permission mappings".

Regarding scalability of Resources in particular, see SAK-3894.

Site running on a free Atlassian Confluence Open Source Project License granted to Sakai Foundation. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) - Bug/feature request - Contact Administrators