JM Metrics

Runtime Test Tool Metrics

I have added some server metrics output to the running controller script. This allows you to keep an eye on your test tool servers as the test is running. This can sometimes be crucial, especially with JMeter, which can be resource hungry.

In practice, in the modern world (!) CPU and Memory are often not as useful as they used to be. With VMs and hyperthreading CPU often isn't correct and Memory isn't so useful for java apps - it could be useful for native apps.

But average load (processor queue length) is useful, so I've reported it here. It could also be useful to plot gc stats for jmeter. This could be added by running jstat or similar over ssh - see below.

For this release, I print out the controller and injector load average for each screen output iteration:


Standard output (highlighted) shows:


jstat could be used to add GC stats. I would find the jmeter process id with:

    ps -ef| grep ApacheJMeter | grep -v grep | awk '{print $2}'

and feed that into jstat and print a few lines of info. Example output would be something like:


[Home] [About (CV)] [Contact Us] [JMeter Cloud] [JM Highlights] [JM Overview] [JM Control] [JM Inject] [JM Threads] [JM Results] [JM Assertions] [JM TPS] [JM Metrics] [JM Runtime] [JM Collation] [JM Logs] [JM 95th] [JM 95th v2] [JM Jenkins] [JM Corporate] [JM Scripts] [JM Variables] [JM Embedded] [JM Hosts] [JM Running] [JM Example] [JM Versions] [webPageTest] [_64 images] [asset moniitor] [Linux Monitor] [Splunk ETL] [Splunk API] [AWS bash] [LR Rules OK] [LR Slave] [LR CI Graphs] [LoadRunner CI] [LR CI Variables] [LR Bamboo] [LR Methods] [LR CI BASH] [Bash methods] [Jenkins V2] [Streaming vid] [How fast] [Finding Issues] [Reporting] [Hand over] [VB Scripts] [JMeter tips] [JMeter RAW] [Dynatrace] [Documents] [FAQ] [Legal]

In the Cartesian Elements Ltd group of companies