Latency issue while running jmeter scripts in AWS server

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Latency issue while running jmeter scripts in AWS server

Hareesh paruchuri
Below is the scenario:

   1. I'm running jmx script using non-gui mode.
   2. 1st iteration result is getting high average response (7 secs) with
   highest latency(1.5 secs).
   3. 2nd, 3rd, & 4th iteration results are giving less average response
   (3.5 secs) with low latency (400 ms). As latency reduces average response
   time reduced.
   4. If I restart my server and run same jmx file again repeating steps 2
   & 3.

Q1: Is it really a problem with Network Latency. If so how to handle this?
Q2: Is it anyway related to Cache then I have used DNS Cache Manager,
Cookie Manager, Cache Manager? Is there anything I forgot?
Thanks & Regard's
P.Hareesh
Reply | Threaded
Open this post in threaded view
|

Re: Latency issue while running jmeter scripts in AWS server

Ivan Rancati-3
hi,
at a first look I'd say Jmeter is behaving correctly like, for example, a
browser would do: the first request takes longer, the following ones are
cached.
Another possibility: the first time you resolve the hostname of the server
there is a dns lookup, all following requests are faster because the ip
address is locally cached.


Assuming your AWS Server is Linux based, you could try the following
1) restart
2) time dig <domain of the server you are testing>
3) time dig <domain of the server you are testing>

and see whether there is a big difference between 2) and 3). If so, and if
the dns server is part of the infrastructure you're testing, you can see if
there is room for optimization there. Be careful to optimize your servers,
and not the clients you use for testing.

Hope this helps,
Ivan

On Wed, Mar 20, 2019 at 12:47 PM Hareesh paruchuri <
[hidden email]> wrote:

> Below is the scenario:
>
>    1. I'm running jmx script using non-gui mode.
>    2. 1st iteration result is getting high average response (7 secs) with
>    highest latency(1.5 secs).
>    3. 2nd, 3rd, & 4th iteration results are giving less average response
>    (3.5 secs) with low latency (400 ms). As latency reduces average
> response
>    time reduced.
>    4. If I restart my server and run same jmx file again repeating steps 2
>    & 3.
>
> Q1: Is it really a problem with Network Latency. If so how to handle this?
> Q2: Is it anyway related to Cache then I have used DNS Cache Manager,
> Cookie Manager, Cache Manager? Is there anything I forgot?
> Thanks & Regard's
> P.Hareesh
>