Parameters considered in JMeter Performance testing :
- CPU usage
- Memory usage – Memory leakages, thread leakage
- All queues and IO waits
- Bottlenecks – Memory, cache, process, processor, disk and network
- Network Usage – Bytes, packets, segments, frames received and sent per sec, Bytes
- Total/sec, Current Bandwidth Connection Failures, Connections Active, failures at
- Network interface lever and protocol level
- Database Problem -Settings and configuration, Usage, Read/sec, Write/sec, any locking, queries, compilation error
- Web server – request and response per seconds, services succeeded and failed, server problem if any.
- Response Time
- Screen transition
- Time – Session time, reboot time, printing time, transaction time, task execution time
- Hits per second, Request per seconds, Transaction per seconds
- Performance measurement with number of users.
- Performance measurement with other interacting application or task
Most of the listeners perform several roles in addition to “listening” to the test results
Listeners can use a lot of memory if there are a lot of samples. Most of the listeners currently keep a copy of every sample in their scope.
The Graph Results listener generates a simple graph that plots all sample times
The throughput number represents the actual number of requests/minute the server handled
|JMeter Graph Results|
Data – plot the actual data values
Average – plot the Average
Median – plot the Median (midway value)
Deviation – plot the Standard Deviation(a measure of the variation)
Throughput – plot the number of samples per unit of time
The aggregate report creates a table row for each differently named request in your test.
Once the test is done, the throughput is the actual through for the duration of the entire test.
The throughput is calculated from the point of view of the sampler target.
Analyzing the Results Using Aggregate report
Label – The label of the sample.
Samples – The number of samples with the same label
Average – The average time of a set of results
Median – The Median is the time in the middle of a set of results. 50% of the samples took no more than this time; the remainder took at least as long.
90% Line – 90% of the samples took no more than this time. The remaining samples at least as long as this. (90 th percentile)
Min – The shortest time for the samples
Max – The longest time for the samples
Error % – Percent of requests with errors
Throughput – the Throughput is measured in requests per second/minute/hour. The time unit is chosen so that the displayed rate is at least 1.0. When the throughput is saved to a CSV file, it is expressed in requests/second, i.e. 30.0 requests/minute is saved as 0.5.
Kb/sec – The throughput measured in Kilobytes per secon