Difference between revisions of "WeBWorK performance"

From WeBWorK_wiki
Jump to navigation Jump to search
Line 34: Line 34:
   
 
non valid response = 0: 0%
 
non valid response = 0: 0%
 
   
   
Line 65: Line 64:
 
* From the Missouri server 32 bit freebsd 7.2 vm with 4GB of ram serving about 1400 students per semester from May 5 2010 to Oct 10 2011:
 
* From the Missouri server 32 bit freebsd 7.2 vm with 4GB of ram serving about 1400 students per semester from May 5 2010 to Oct 10 2011:
   
count = 4664624
+
count = 4664624
under 0.1 seconds = 3696211: 79.2%
+
under 0.1 seconds = 3696211: 79.2%
between 0.1 and 0.2 seconds = 536336: 11.5%
+
between 0.1 and 0.2 seconds = 536336: 11.5%
between 0.2 and 0.5 seconds = 363331: 7.8%
+
between 0.2 and 0.5 seconds = 363331: 7.8%
between 0.5 and 1.0 seconds = 48816: 1%
+
between 0.5 and 1.0 seconds = 48816: 1%
between 1.0 and 2.0 seconds = 13498: 0.3%
+
between 1.0 and 2.0 seconds = 13498: 0.3%
between 2.0 and 3.0 seconds = 2865: 0.1%
+
between 2.0 and 3.0 seconds = 2865: 0.1%
between 3.0 and 4.0 seconds = 1406: 0%
+
between 3.0 and 4.0 seconds = 1406: 0%
between 4.0 and 5.0 seconds = 666: 0%
+
between 4.0 and 5.0 seconds = 666: 0%
between 5.0 and 10.0 seconds = 1036: 0%
+
between 5.0 and 10.0 seconds = 1036: 0%
over 10.0 seconds = 459: 0%
+
over 10.0 seconds = 459: 0%
non valid response = 0: 0%
+
non valid response = 0: 0%
   
 
'''Note''': This server had two "out of memory" events which brought the server down due to a freebsd kernel setting that we should have tweaked but didn't until we understood the problem. This isn't a concern with the linux kernel or 64bit freebsd machines. These two events probably account for most of the requests on the high end.
 
'''Note''': This server had two "out of memory" events which brought the server down due to a freebsd kernel setting that we should have tweaked but didn't until we understood the problem. This isn't a concern with the linux kernel or 64bit freebsd machines. These two events probably account for most of the requests on the high end.

Revision as of 11:00, 5 October 2011

The timing log

The timing_log_performance.pl is available in webwork2/bin and parses the timing log data found in webwork2/logs/timing.log.

To run the script, cd to the WeBWorK logs directory (usually /opt/webwork/webwork2/logs) and enter the command: timing_log_check.pl


Data

  • From the courses.webwork.maa.org timing log:

Data from July 2010 - August 2011 count = 13427151

under 0.1 seconds = 7999616: 59.6%

between 0.1 and 0.2 seconds = 2864257: 21.3%

between 0.2 and 0.5 seconds = 1955285: 14.6%

between 0.5 and 1.0 seconds = 297585: 2.2%

between 1.0 and 2.0 seconds = 135471: 1%

between 2.0 and 3.0 seconds = 45002: 0.3%

between 3.0 and 4.0 seconds = 23265: 0.2%

between 4.0 and 5.0 seconds = 13663: 0.1%

between 5.0 and 10.0 seconds = 30677: 0.2%

over 10.0 seconds = 62330: 0.5%

non valid response = 0: 0%


  • From the Rochester server math.webwork.rochester.edu timing log:

Data from September 6, 2011 count = 2586

under 0.1 seconds = 1795: 69.4%

between 0.1 and 0.2 seconds = 223: 8.6%

between 0.2 and 0.5 seconds = 515: 19.9%

between 0.5 and 1.0 seconds = 36: 1.4%

between 1.0 and 2.0 seconds = 8: 0.3%

between 2.0 and 3.0 seconds = 8: 0.3%

between 3.0 and 4.0 seconds = 1: 0%

between 4.0 and 5.0 seconds = 0: 0%

between 5.0 and 10.0 seconds = 0: 0%

over 10.0 seconds = 0: 0%

non valid response = 0: 0%

  • From the Missouri server 32 bit freebsd 7.2 vm with 4GB of ram serving about 1400 students per semester from May 5 2010 to Oct 10 2011:

count = 4664624 under 0.1 seconds = 3696211: 79.2% between 0.1 and 0.2 seconds = 536336: 11.5% between 0.2 and 0.5 seconds = 363331: 7.8% between 0.5 and 1.0 seconds = 48816: 1% between 1.0 and 2.0 seconds = 13498: 0.3% between 2.0 and 3.0 seconds = 2865: 0.1% between 3.0 and 4.0 seconds = 1406: 0% between 4.0 and 5.0 seconds = 666: 0% between 5.0 and 10.0 seconds = 1036: 0% over 10.0 seconds = 459: 0% non valid response = 0: 0%

Note: This server had two "out of memory" events which brought the server down due to a freebsd kernel setting that we should have tweaked but didn't until we understood the problem. This isn't a concern with the linux kernel or 64bit freebsd machines. These two events probably account for most of the requests on the high end.

Load monitoring software

Webmin on courses.maa.org

load on courses.webwork.maa.org 30 Aug 11 - 6 Sept 11