Hi,
I've previously seen bad performance form Akka HTTP for a simple ping/pong
scenario (which I realize according to the release notes is still a
relatively bad scenario for Akka HTTP), but the results I'm getting are bad
enough that I'm wondering if my test is even valid.
Here's my code:
pa
Without looking at the code, two things to fix right away in your
methodology:
1) You're running `ab` without persistent connections (also known as
"useless mode").
Please run: `ab -k` to use keep-alive connections, which is what all http
clients and browsers do.
2) Please do not benchmark using
Also, I'd recommend avoiding App for benches, I don't know how it works
nowadays but I recall seeing issues with inlining (OSR) back in the day.
On Tue, Sep 6, 2016 at 4:38 PM, Konrad Malawski <
konrad.malaw...@lightbend.com> wrote:
> Without looking at the code, two things to fix right away in y
And it can be considered recommended to use wrk2 over wrk (coordinated
omission correction)
On Tue, Sep 6, 2016 at 4:43 PM, Viktor Klang wrote:
> Also, I'd recommend avoiding App for benches, I don't know how it works
> nowadays but I recall seeing issues with inlining (OSR) back in the day.
>
>
Thanks!
Adding -k indeed fixes this right away:
ab -k -c 400 -n 10 -m GET http://127.0.0.1:3000/
This is ApacheBench, Version 2.3 <$Revision: 1706008 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
