| Note |
|---|
Tracking known Sakai performance issues that we need need to address |
sakai_2-5-x
sakai_2-4-x
- Lance's response to "UC Berkeley in crisis"
No Format There has been a lot of excellent input on this issue. I would add the following comments: 1) Do not discount the possibility of SAK-8932 as Stephen Marquard suggested. This issue is not limited to Chat but can be triggered by any JSF application AFAIK. The stuck threads could lead to the kind of request backlogs you are reporting. We have only seen this crop up once or twice, but it does seem to be load related so you may be seeing it in your environment. 2) Hardware is cheap - Since we have upgraded to eight servers with 10GB heaps (i.e. total 80GB heap), Sakai is behaving *MUCH* better under load. Our hardware change included moving from 32bit to 64bit OS, cutting the number of app servers in half (i.e. 16 --> 8), keeping the total number of CPUs in the cluster at 32, and going from 32GB total heap to 80GB. 3) Are you seeing any OutOfMemoryExceptions? Before our 64bit upgrade, we were seeing 10 - 15 of these a day. Since the upgrade, I have not seen one OOM error. 4) Turning off quotas does significantly reduce the amount of XML DOM parsing you will do, but it was not a major contributing factor to our stability. Let us know what we can do to help... L
- Stanford: Critical performance problems in production. Please help!
...