[Building Sakai] Sakai scalability monitoring and testing

[Ray Davis]

We fairly quickly found a bug in the Gradebook Course Grades logic 
(since fixed) thanks to JAMon's DB query stats, and were able to verify 
improvement in the All Grades logic with straight timing stats. DBCP 
connection pool stats pointed out a potentially expensive mistake in the 
comments to the components.xml for the old "db" area. We also found ways 
to improve our local use of EhCache, but haven't put them in place -- it 
turns out that we're currently more bottlenecked on CPU and memory 
contention than on DB, and so when we started using Tomcat-resident DB 
caching "more effectively," our throughput actually went down. :)

Best,
Ray

On 3/10/2009 9:51 AM, Stephen Marquard wrote:
> Hi Ray,
> 
> Great to see more work in this area.
> 
> What sort of problems have you found & fixed as a result?
> 
> Regards
> Stephen
> 
>>>> Ray Davis <ray at media.berkeley.edu> 2009/03/09 07:46 PM >>>
> Lately at UC Berkeley we've been trying to better understand (and 
> hopefully reduce) our ongoing performance and scalability woes. Some 
> sakai-dev readers might be interested in the code we've recently checked 
> into the Subversion repository, since it's already uncovered a couple of 
> bugs and cleared up some lingering questions. 
> 
> ...
>