
|
If you were logged in you would be able to see more operations.
|
|
|
Sakai
Created: 27-Aug-2007 08:07
Updated: 23-Oct-2008 07:47
|
|
| Component/s: |
Mailtool
|
| Affects Version/s: |
2.4.x
|
| Fix Version/s: |
None
|
|
| 2.4.x Status: |
None
|
| 2.5.x Status: |
None
|
| 2.6.x Status: |
None
|
|
The mailtool does a user lookup of every site participant when it loads, even if the users are not to be displayed. If Sakai stores all user directory information in a local DB this extra performance hit may be negligible, but if you're configured to do an LDAP lookup (especially for a large course) the initial load time can be horrendous. This is a severe performance issue for large courses, one which prevents us from recommending the tool to our faculty.
It would be better if those lookups are only performed when a list is "expanded," and then have them cached. This would at least break it down into bite-sized pieces, and make the initial load time tolerable.
|
|
Description
|
The mailtool does a user lookup of every site participant when it loads, even if the users are not to be displayed. If Sakai stores all user directory information in a local DB this extra performance hit may be negligible, but if you're configured to do an LDAP lookup (especially for a large course) the initial load time can be horrendous. This is a severe performance issue for large courses, one which prevents us from recommending the tool to our faculty.
It would be better if those lookups are only performed when a list is "expanded," and then have them cached. This would at least break it down into bite-sized pieces, and make the initial load time tolerable. |
Show » |
|
Updated Info: http://bugs.sakaiproject.org/confluence/display/MAILTOOL/Home