Differences between revisions 17 and 18
Revision 17 as of 2012-10-09 03:18:55
Size: 2394
Comment:
Revision 18 as of 2012-10-09 03:58:00
Size: 3081
Comment: Add a Test with clean shutdown
Deletions are marked like this. Additions are marked like this.
Line 91: Line 91:


== JMeter 2.8 Additional Test (to check time taken is fine) ==

 * In this test, to let threads complete, we increase Test Duration to check no delay happens which can reveal abnormal behaviour.
 * Test Plan same as before with following changes:
  * Ramp-up period : 100 seconds
  * Number of Threads : 1500
  * Scheduler checked:
   * Duration: 800 seconds (So all threads should complete before that time)
   * Startup Delay : 7 seconds

=== Test Plan for additional Test: ===

Test Plan used :

[[attachment:PerformancePlan-2.8.jmx]]

=== Transactions: ===

{{attachment:Transactions-2.8-additional.png}}

=== Conclusion ===

No delay, everything is OK.

JMeter Performance evolution across versions (>= 2.5.1)

This article is the record of a Test done in the following conditions:

  • Tomcat version 6.0.24
  • Tomcat JVM : -Xms256m -Xmx1024m
  • JMeter JVM : -Xmx512m
  • Set session timeout in web.xml to 1 minute
  • Java version "1.6.0_29"
  • Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-10M3527)
  • Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode)

  • Mac OS 10.6.8
  • JMeter and Tomcat on same machine
  • No particular OS Tuning
  • RAM : 8 Go 1067 MHz DDR3
  • Processor : 3.06 GHz Intel Core 2 Duo
  • No swap
  • Simple Test plan using Tomcat examples
  • Test Plan:
    • Ramp-up period : 100 seconds
    • Number of Threads : 1500
    • Scheduler checked:
      • Duration: 10 minutes (So test will run just 10 minutes forcing stop at 10th minute)
      • Startup Delay : 7 seconds
  • CSV output

Test Plan:

Test Plan used : TestPlan.jmx

JMETER 2.5.1

Transactions:

Transactions-2.5.1.png

JVM Behaviour:

JVM-State-2.5.1.png

GC Activity:

  • GC activity is much higher with around 5 GC CPU peaks every 2 minutes
  • and 20 FULL GC of 700 to 800 ms each
  • Throughput: 97,71%
  • Pauses : 13,69s
  • Memory Cleaned : 391m/min
  • Full GC tend to be much more frequent at end of test

JMETER 2.6:

Transactions:

Transactions-2.6.png

JVM Behaviour:

JVM-State-2.6.png

JMETER 2.7:

Transactions:

Transactions-2.7.png

JVM Behaviour:

JVM-State-2.7.png

GC Activity:

  • No GC CPU peak,
  • 1 FULL GC
  • Throughput:98.54

  • Pauses : 8.9s
  • Memory cleaned: 1108m /min

JMETER 2.8:

Transactions:

Transactions-2.8.png

Graph Limiting 150 points in row:

Transactions-2.8-150-points.png

JVM Behaviour:

JVM-State-2.8.png

GC Activity:

  • No GC CPU peak,
  • No FULL GC
  • Throughput:98.89%

  • Pauses : 6.72s
  • Memory cleaned: 1391m /min

Conclusion

  • No significant improvement between 2.6 and 2.5.1
  • Significant improvement between 2.7 and 2.6
  • Significant improvement between 2.8 and 2.7
  • Better memory behaviour
  • More accurate response times with High Load

JMeter 2.8 Additional Test (to check time taken is fine)

  • In this test, to let threads complete, we increase Test Duration to check no delay happens which can reveal abnormal behaviour.
  • Test Plan same as before with following changes:
    • Ramp-up period : 100 seconds
    • Number of Threads : 1500
    • Scheduler checked:
      • Duration: 800 seconds (So all threads should complete before that time)
      • Startup Delay : 7 seconds

Test Plan for additional Test:

Test Plan used :

PerformancePlan-2.8.jmx

Transactions:

Transactions-2.8-additional.png

Conclusion

No delay, everything is OK.

JMeterPerformance (last edited 2012-10-09 03:58:00 by Philippe Mouawad)