jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepak Shetty <>
Subject Re: Capturing request-send-time and response-receive-time
Date Fri, 16 Nov 2018 01:35:12 GMT
In all probability the answer is that JMeter cannot capture these values
that you are asking for -One reason for that is that HTTP and TCP probably
doesnt work the way whoever asked for   "time-taken-to-sendrequest" and
"time-taken-to-receive-response" is envisaging.

>In a step-up-load-test we observed that "Latency" and "Connect time" is
>almost constant with increased user load but "Elapsed time" kept
>increasing. Leaving no clue where we are losing time.
The 2 things you are requesting probably wont give you that clue either.
Your most likely cause is your application is slowing down under load and
the easiest way is to log the response time as your application sees it in
your application. If you are running through a webserver like apache/nginx
(even if you actual application is something else) then they can easily log
the duration of the response too. If it shows the same increase then your
problem is within your application and you will need to run an application
specific profiler.
In some cases you might see problems with your network and/or your JMeter
test tool itself . For JMeter you can do one of 2 things - run tools on the
JMeter machine itself and see whether its healthy - alternately split your
load into multiple JMeter clients and if you see improvements then you have
a problem on your test tool side. If it behaves the same then likely you
dont have a JMeter client issue. I also usually like to independently
verify that I am seeing on the browser what JMeter is reporting while the
test is being run (i.e. when your JMeter is reporting that a page is taking
X seconds and the test is running , and you access the site using an
independent browser , does it report a value close to X) till I have
confidence in the script and run

JMeter is a test and simulation tool - It can mostly tell you a problem
exists - it cant tell you what the problem exactly is - that is a different


On Wed, Nov 14, 2018 at 7:40 PM Prasad K <> wrote:

> Friends please check this question and share your thoughts/inputs.
> On Tue, 13 Nov 2018 at 15:01, Prasad K <> wrote:
> > Hi,
> >
> > We are using Simple Data Write
> > <
> >
> > listener to capture test results. In the captured results I would like to
> > have detailed stats for Round-trip-time (RTT). In the "Sample Results
> Save
> > Configuration" we already have "Connect time" and "Server latency". In
> > addition to that I would like also to have "time-taken-to-sendrequest"
> and
> > "time-taken-to-receive-response". With these stats I would like to know
> if
> > we are loosing time in sending request and/or receiving response.
> >
> > In a step-up-load-test we observed that "Latency" and "Connect time" is
> > almost constant with increased user load but "Elapsed time" kept
> > increasing. Leaving no clue where we are losing time. With the above
> > mentioned counters I expecting more clues.
> >
> > Regards,
> > Prasad.
> >

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