Fwd: 2-5-x in full production

[Michelle D'Souza]

Just in case anyone isn't on the Sakai list. Way to go on the 'My  
Active Sites' design!

Michelle

Begin forwarded message:

> From: "Stephen Marquard" <stephen.marquard at uct.ac.za>
> Date: February 22, 2008 12:01:54 PM EST (CA)
> To: <sakai-dev at collab.sakaiproject.org>, <sakai- 
> qa at collab.sakaiproject.org>
> Subject: 2-5-x in full production
>
> Hi all,
>
> Today is the end of the first week of term, with our Sakai 2-5-x  
> instance under full load (for us). This is approx distinct 9000  
> users logging in per day, and a peak of 1766 sessions (stats at  
> https://vula.uct.ac.za/web/dev/dashboard/)
>
> Overall, things went smoothly. Judging from the mix of support  
> calls which we've received, the 'My Active Sites' popup has  
> eliminated almost all of the "I can't find my site" (= didn't click  
> on the -more- drop-down) problems.
>
> On the performance front, we only had one significant issue which  
> caused about an hour of seriously degraded response, which is  
> Section Info: SAK-13021. This is in fact not a new issue and has  
> affected us in the past, but we'll be putting some work into  
> resolving it before our next start of term in Jul 08.
>
> It's slightly too early to get solid performance data on all tools,  
> as at the start of the academic year, most courses are starting off  
> with new sites (i.e. not much data in them yet).
>
> On the quality front, our automatic analysis of email bug reports  
> (https://vula.uct.ac.za/web/dev/dashboard/bugs.html and https:// 
> vula.uct.ac.za/mrtg/bug-summary.html) shows about 70 distinct bugs  
> that result in stack traces for users, affecting between 0.3% and  
> 0.7% of the user population (in a 24 hr period). This doesn't count  
> tools which never surface their stack traces to the portal error  
> handler (e.g. some RSF tools like Polls), or ERRORs or stack traces  
> that only show up in catalina.out, and we're also not using the  
> complete toolset (e.g. only Glossary from OSP, and we don't have  
> mailtool or blogger in our build).
>
> What do you think is an appropriate target for bugs in Sakai  
> production instances? Once 2.5.0 is released, perhaps we could work  
> towards a quality target for 2.5.1 based on some bug-incidence  
> metrics from 2-5-x production sites.
>
> Cheers
> Stephen
>
>
>
> Stephen Marquard, Learning Technologies Co-ordinator
> Centre for Educational Technology, University of Cape Town
> http://www.cet.uct.ac.za ( http://www.cet.uct.ac.za/ )
> Email/IM/XMPP: stephen.marquard at uct.ac.za
> Phone: +27-21-650-5037 Cell: +27-83-500-5290
> [see attachment: "message0.html", size: 2888 bytes]
>
>
> Attachments:
>
> message0.html
> https://collab.sakaiproject.org/access/content/attachment/ 
> 50891749-0268-43f9-00c9-0879a73a5dea/message0.html
>
> ----------------------
> This automatic notification message was sent by Sakai Collab  
> (https://collab.sakaiproject.org/portal) from the DG: Development  
> (a.k.a. sakai-dev) site.
> You can modify how you receive notifications at My Workspace >  
> Preferences.
>

------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080228/8a500bca/attachment.html>