Skip to end of metadata
Go to start of metadata

Single Ubuntu 10.04 64 bits

Hardware

  • 8 x 2.4 GHz Core Bare Metal Instance - 8 GB Ram [See softlayer.com cloud computing]

Software

  • MySQL Server 5.5.11
  • Java JDK 1.6.0_24
  • JBoss 4.0.2 (LAMS 2.3.5 Server)

Relevant configuration files

server.xml

      <Connector port="8080" address="${jboss.bind.address}" URIEncoding="UTF-8"
         maxThreads="1024" strategy="ms" maxHttpHeaderSize="8192"   acceptCount="600" connectionTimeout="500" 
         emptySessionPath="true"
         enableLookups="false" redirectPort="8443" minSpareThreads="25" maxSpareThreads="75" 
         disableUploadTimeout="true"/>

run.bat

set JAVA_OPTS=%JAVA_OPTS% -server -Xms1024m -Xmx2048m -XX:MaxPermSize=130m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=95 

Test harness

As all our previous scalability tests, we use the test harness to simulate users load. Learner's configuration mindelay = 15, maxdelay = 90. Sequence: 10forums.zip.

Attached is the test harness used for this test.

Results

We ran three tests with 500, 800 and 1000 concurrent users.

500 concurrent users

Test sequence: 10forums.zip sequence that contains ten forums activities on a row
Using 10 instances of the test harness from 10 separate boxes simulating 50 users each, we've got the following results:

instance

Average response (in seconds)

z01

0.562080543669771

z02

0.5625217502558854

z03

0.5561957232704403

z04

0.5626616352201258

z05

0.5563408004027184

z06

0.5576121318902593

z07

0.5617619526925013

z08

0.5572287367891293

z09

0.5570665154950869

z10

0.560719496855346

Total Average:

0.559418929

So for every page request, with 500 users in LAMS at the time, the cluster is able to responde in 0.56 second in average.

800 concurrent users

Testing sequence: 10forums.zip sequence that contains ten forums activities on a row
Using 10 instances of the test harness from 10 separate boxes simulating 80 users each, we've got the following results:

instance

Average response (in seconds)

z01

0.6748560844892812

z02

0.6730291734197731

z03

0.6514725054989002

z04

0.6789197115384615

z05

0.6744407463439234

z06

0.6783658852061439

z07

0.6689276495182694

z08

0.6802769546027743

z09

0.6698830658368817

z10

0.6610661554921541

Total Average:

0.671123793

So for every page request, with 800 users in LAMS at the time, the cluster is able to responde in 0.67 second in average.

1000 concurrent users

Testing sequence: 10forums.zip sequence that contains ten forums activities on a row
Using 10 instances of the test harness from 10 separate boxes simulating 100 users each, we've got the following results:

instance

Average response (in seconds)

z01

0.7982902574457345

z02

0.8115823361082206

z03

0.8227295904151574

z04

0.8152740149369044

z05

0.7994750754201982

z06

0.8392842212592404

z07

0.8164942960676419

z08

0.8186477600209588

z09

0.809012216173151

z10

0.7945676973881717

Total Average:

0.812535747

So for every page request, with 1000 users in LAMS at the time, the cluster is able to responde in 0.81 second in average.

Raw results

500 concurrent users

500

z1

	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2233.146 seconds
	Average response time: 0.562080543669771 seconds

z5
	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2210.342 seconds
	Average response time: 0.5563408004027184 seconds

z7
	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2232.442 seconds
	Average response time: 0.5617619526925013 seconds


z9
	50 learner(s) attended, 49 finished and 1 aborted.
	Total response time: 2210.997 seconds
	Average response time: 0.5570665154950869 seconds

z10
	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2228.86 seconds
	Average response time: 0.560719496855346 seconds

z2
	50 learner(s) attended, 49 finished and 1 aborted.
	Total response time: 2198.335 seconds
	Average response time: 0.5625217502558854 seconds

z4
	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2236.58 seconds
	Average response time: 0.5626616352201258 seconds

z6
	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2215.393 seconds
	Average response time: 0.5576121318902593 seconds

z8
	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2214.427 seconds
	Average response time: 0.5572287367891293 seconds

z3
	50 learner(s) attended, 50 finished and 0 aborted.
	Total response time: 2210.878 seconds
	Average response time: 0.5561957232704403 seconds

800 concurrent users

z1
	80 learner(s) attended, 80 finished and 0 aborted.
	Total response time: 4281.287 seconds
	Average response time: 0.6748560844892812 seconds

z2
	80 learner(s) attended, 77 finished and 3 aborted.
	Total response time: 4152.59 seconds
	Average response time: 0.6730291734197731 seconds

z3
	80 learner(s) attended, 63 finished and 17 aborted.
	Total response time: 3258.014 seconds
	Average response time: 0.6514725054989002 seconds

z4
	80 learner(s) attended, 78 finished and 2 aborted.
	Total response time: 4236.459 seconds
	Average response time: 0.6789197115384615 seconds

z5
	80 learner(s) attended, 75 finished and 5 aborted.
	Total response time: 4012.248 seconds
	Average response time: 0.6744407463439234 seconds

z6
	80 learner(s) attended, 78 finished and 2 aborted.
	Total response time: 4195.693 seconds
	Average response time: 0.6783658852061439 seconds

z7
	80 learner(s) attended, 69 finished and 11 aborted.
	Total response time: 3679.771 seconds
	Average response time: 0.6689276495182694 seconds

z8
	80 learner(s) attended, 80 finished and 0 aborted.
	Total response time: 4315.677 seconds
	Average response time: 0.6802769546027743 seconds

z9
	80 learner(s) attended, 77 finished and 3 aborted.
	Total response time: 4090.306 seconds
	Average response time: 0.6698830658368817 seconds

z10
	80 learner(s) attended, 70 finished and 10 aborted.
	Total response time: 3707.259 seconds
	Average response time: 0.6610661554921541 seconds

1000 concurrent users

z8
	100 learner(s) attended, 96 finished and 4 aborted.
	Total response time: 6249.557 seconds
	Average response time: 0.8186477600209588 seconds

z4
	100 learner(s) attended, 98 finished and 2 aborted.
	Total response time: 6331.418 seconds
	Average response time: 0.8152740149369044 seconds

z6
	100 learner(s) attended, 99 finished and 1 aborted.
	Total response time: 6585.024 seconds
	Average response time: 0.8392842212592404 seconds

z2
	100 learner(s) attended, 97 finished and 3 aborted.
	Total response time: 6239.445 seconds
	Average response time: 0.8115823361082206 seconds

z3
	100 learner(s) attended, 89 finished and 11 aborted.
	Total response time: 5905.553 seconds
	Average response time: 0.8227295904151574 seconds

z5
	100 learner(s) attended, 87 finished and 13 aborted.
	Total response time: 5565.146 seconds
	Average response time: 0.7994750754201982 seconds

z7
	100 learner(s) attended, 94 finished and 6 aborted.
	Total response time: 6083.699 seconds
	Average response time: 0.8164942960676419 seconds

z9
	100 learner(s) attended, 95 finished and 5 aborted.
	Total response time: 6092.671 seconds
	Average response time: 0.809012216173151 seconds

z10
	100 learner(s) attended, 84 finished and 16 aborted.
	Total response time: 5293.41 seconds
	Average response time: 0.7945676973881717 seconds

z1
	100 learner(s) attended, 100 finished and 0 aborted.
	Total response time: 6325.652 seconds
	Average response time: 0.7982902574457345 seconds