jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Swor <sworisbreath...@gmail.com>
Subject Re: Backend Listener and reduced throughput
Date Wed, 16 Dec 2015 13:38:31 GMT
Generally speaking, performance degradation is a known issue with all
listeners (more processing = more cpu cycles consumed per loop). However,
with the GraphiteBackendListener(
https://github.com/apache/jmeter/blob/v2_13/src/components/org/apache/jmeter/visualizers/backend/graphite/GraphiteBackendListenerClient.java),
there seems to be a lot of thread synchronization going on, which could
potentially be contributing to a performance degradation. It's hard to say
for sure, though, without doing some actual measurements on it.

On Wed, Dec 16, 2015 at 8:45 PM, Bhadauria, Tarun Kumar <
tarun.kumar.bhadauria@zalando.de> wrote:

> Test Summary -
>
> Jmeter Version - 2.13
> Jmeter Machines - 10 AWS EC2 m4.4xlarge instances
> Number of threads on each instance 72 hence in total 720 threads in
> distributed mode
> Test is executed in non GUI mode
>
> I was experimenting with Backend listener as described here
> <http://jmeter.apache.org/usermanual/realtime-results.html> and came
> across
> drastic reduction in throughput against a static html file. These are the
> results are received for 5 minutes test -
>
> Throughput with backend listener - 5000/sec
> Throughput without backend listener - 9800/sec
>
> I have repeated the test over a period of one week and test results have
> been consistent.
>
> I did not see any significant difference in load avg or cpu utilization on
> load agents with or without backend listener.
>
> Is JMeter performance degradation a known issue with Backend listener?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message