You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to compare the latency difference between Locust and Hey Tool for my Node JS app and I see a Hey tool latency is 10x higher than Locust. It is the same end point and it is the same RPS I am trying to send. I see the latency to be same with 1 user/10 users but when I increase with 500 users and 600 users I see the difference to be pretty high. Not sure what is happening in Hey tool that is making the service overloaded and resulting in very high latency. It is a simple GET request. Also I see a lot of variability in terms of latency with Hey tool.
The text was updated successfully, but these errors were encountered:
I am trying to compare the latency difference between Locust and Hey Tool for my Node JS app and I see a Hey tool latency is 10x higher than Locust. It is the same end point and it is the same RPS I am trying to send. I see the latency to be same with 1 user/10 users but when I increase with 500 users and 600 users I see the difference to be pretty high. Not sure what is happening in Hey tool that is making the service overloaded and resulting in very high latency. It is a simple GET request. Also I see a lot of variability in terms of latency with Hey tool.
The text was updated successfully, but these errors were encountered: