Re: [akka-user] Re: Akka HTTP performance for short lived connections

Great, thanks for the update. We have other ideas for how to improve this and will get to it, eventually. There was a quick attempt previously, but it had to be abandoned because of more urgent things. If someone would like to take a stab at it this might be a good starting point:

Re: [akka-user] Re: Akka HTTP performance for short lived connections

Small update - disabling auto fuse, or pre-fusing (with & without auto fusing) has an effect (BTW I could not find a way to do this with the java). Performance is improved by up to 50%. However, it's still not in the same order of magnitude as other libraries. It's still at least 1 second for

Re: [akka-user] Re: Akka HTTP performance for short lived connections

Yeah, no code is rather silly really... I've created this repository: https://github.com/adamhonen/Akka-Http-performance-test I didn't get a chance to try the suggestions above yet, though. On Monday, April 18, 2016 at 10:25:00 PM UTC+3, Konrad Malawski wrote: > > I see some results, but no

Re: [akka-user] Re: Akka HTTP performance for short lived connections

I see some results, but no code that is being benchmarked – please always post benchmarked code together with benchmark, otherwise it's hard to tell what's actually going on. On Mon, Apr 18, 2016 at 9:19 PM, Johan Andrén wrote: > Yet another thing to test could be to

[akka-user] Re: Akka HTTP performance for short lived connections

Yet another thing to test could be to pre-fuse your Request => Response flow, first, and then run that with autoFusing turned on or off. Locally I get the best improvement with pre-fusing and no autoFusing. Looks like this: implicit val materializer =

[akka-user] Re: Akka HTTP performance for short lived connections

One thing that could be interesting to try out if you want to achieve as high throughput as possible where each new request is a new connection with the current akka-http version is to disable autoFusing (which is pretty costly). That can be done when you create the materializer like this:

[akka-user] Re: Akka HTTP performance for short lived connections

Adam, thanks! Very informative. I also have found handy to use almost empty response to estimate the whole request-response chain itself (starting from now abandoned tiscaf [1] and rising rps up to almost 90K on humble workstation :) ). [1] http://gaydenko.com/scala/tiscaf/httpd/ --

[akka-user] Re: Akka HTTP performance for short lived connections

Adam, just curious, can you, please, supply some example ApacheBench output? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives: