[sakai2-tcc] Roster tool clarification.

[Berg, Alan]

Hi all,

Seth is running long burning, low level stress tests on the Columbia QA server.  For a large site, Roster is behaving very poorly, taking more than 5 minutes to return. Therefore, the reason I e-mail, is that Roster has known performance issues and there was/is a discussion about Roster to be replaced. It is late in the cycle so I am assuming that it better to ask for a review of optimizations rather than to replace. However, it is the TCC's role to decide the roadmap.

In confluence: http://confluence.sakaiproject.org/display/TCC/List+of+Planned+2.8.0+Changes

New Roster tool
               Lancaster has rewritten the original Roster tool. A separate
e-mail describing the technical details has been sent to the TCC for
evaluation and discussion.

http://sakai-project-mail-list-archives.1343168.n2.nabble.com/sakai2-tcc-Roster-tool-changes-td5440100.html
http://jira.sakaiproject.org/browse/RSTR-3



The relevant Jira is:
http://jira.sakaiproject.org/browse/SAK-19588

Is my approach correct?

Alan

Alan Berg
QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20101129/515523da/attachment.html