[Building Sakai] [samigo-team] Monitoring Samigo in a big test

Stephen Marquard stephen.marquard at uct.ac.za
Sat May 24 06:47:51 PDT 2014


How many sites are running SAK-25677 in production? Any experience with this change with large, high-stakes testing (300+ concurrent users)?

Cheers
Stephen

________________________________________
From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of John Bush [jbush at anisakai.com]
Sent: 23 May 2014 10:20 PM
To: Sam Ottenhoff
Cc: sakai-dev; samigo-team at collab.sakaiproject.org
Subject: Re: [Building Sakai] [samigo-team] Monitoring Samigo in a big test

2nd that, pick up that stuff, we had similiar issues, since moving JSF
client side state, much better.

On Fri, May 23, 2014 at 6:35 AM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
> I strongly recommend checking out the tiny Samigo patch in this JIRA that
> moved JSF view state from server to client:
>
>   https://jira.sakaiproject.org/browse/SAK-25677
>
>
> On Fri, May 23, 2014 at 7:34 AM, Daniel Merino <daniel.merino at unavarra.es>
> wrote:
>>
>> Hi everybody.
>>
>> Time ago, we had a system crash while one Samigo test was being made by
>> 250+ users. System memory was filled up and our production environment
>> gradually slowed down until it crashed.
>>
>> This happened after using the audio recorder applet, when users uploaded
>> the recorded file all at the same time. After a reboot, another part of
>> the exam with other kind of questions also produced the same system
>> slowness and halt.
>>
>> We use Samigo 2.9.2 on Sakai 2.9.2 and the system which collapsed had
>> the next configuration (1). Now we have extended that system to this one
>> (2).
>>
>> And soon we are going to have another test with a high number of users.
>> We plan to monitor that test and try to look into the results to find
>> what has happened in case it fails. Or maybe send these results to the
>> list so other more expert users can have a look on it.
>>
>> We are going to use YourKit to store the JVM internal use and JConsole
>> to watch memory and CPU usage. If somebody can provide some advice about
>> other tools or procedures that we could use to have better and more
>> useful results, we would be very grateful.
>>
>> Of course, if our configuration has any bottleneck or if any work has
>> been done on this performance topic in Samigo's code, I would like to
>> know in order to fix it here if I can.
>>
>> Many thanks in advance.
>> Best regards.
>>
>> -------------------------------
>>
>> (1) 1 active Tomcat.
>>
>> Processor:
>>
>> http://ark.intel.com/products/27219/Intel-Xeon-Processor-5160-4M-Cache-3_00-GHz-1333-MHz-FSB?wapkw=5160
>>
>> JAVA_OPTS: '-server -d64 -Xms10000m -Xmx10000m -XX:PermSize=512m
>> -XX:MaxPermSize=512m -Djava.awt.headless=true -Dhttp.agent=Sakai
>> -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
>> -Dsun.lang.ClassLoader.allowArraySyntax=true -Duser.language=es
>> -Duser.region=ES -Dsakai.cookieName=SAKAISESSIONID
>> -XX:+UseConcMarkSweepGC -XX:+ExplicitGCInvokesConcurrent
>> -XX:+CMSIncrementalMode'
>>
>> (2) 2 active Tomcat.
>>
>> Processor 1:
>>
>> http://ark.intel.com/products/27219/Intel-Xeon-Processor-5160-4M-Cache-3_00-GHz-1333-MHz-FSB?wapkw=5160
>>
>> Processor 2:
>>
>> http://ark.intel.com/products/52583/Intel-Xeon-Processor-E5606-8M-Cache-2_13-GHz-4_80-GTs-Intel-QPI
>>
>>
>> JAVA_OPTS: '-server -d64 -Xms11000m -Xmx11000m -Xmn3g -XX:PermSize=512m
>> -XX:MaxPermSize=512m -Djava.awt.headless=true -Dhttp.agent=Sakai
>> -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
>> -Dsun.lang.ClassLoader.allowArraySyntax=true -Duser.language=es
>> -Duser.region=ES -Dsakai.cookieName=SAKAISESSIONID
>> -XX:+UseConcMarkSweepGC -XX:+ExplicitGCInvokesConcurrent
>> -XX:+CMSIncrementalMode'
>>
>> --
>> Daniel Merino Echeverría
>> daniel.merino at unavarra.es
>> Gestor de E-learning - Centro Superior de Innovación Educativa.
>> Tfno: 948-168489 - Universidad Pública de Navarra.
>>
>> _______________________________________________
>> samigo-team mailing list
>> samigo-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/samigo-team
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"



--
John Bush
602-490-0470

** This message is neither private nor confidential in fact the US
government is storing it in a warehouse located in Utah for future
data mining use cases should they arise. **
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
________________________________
 UNIVERSITY OF CAPE TOWN

This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity.



More information about the sakai-dev mailing list