[akka-user] Re: Akka http vs Spray performance

Hi, first thank you so much for making such a great piece of software. As the 2.4.0 is out, have you made any progress on improving performance of akka http or at least is there any roadmap for this ? Thanks Jakub On Wednesday, May 27, 2015 at 1:44:49 PM UTC+2, zergood wrote: > > I've done l

[akka-user] Re: Akka http vs Spray performance

Figured I should link to the 2.4.9 annoucement from this old thread (as it shows up high in google). In 2.4.9 we did quite some improvements, annoucement here: http://akka.io/news/2016/08/19/akka-2.4.9-released.html Highlights of the per

[akka-user] Re: Akka http vs Spray performance

I perform some test for 2.4.9 release > wrk -t30 -c64 http://127.0.0.1:9000/dictionaries/hello/suggestions?ngr=hond Running 10s test @ http://127.0.0.1:9000/dictionaries/hello/suggestions?ngr=hond 30 threads and 64 connections Thread Stats Avg Stdev Max +/- Stdev Latency

[akka-user] Re: Akka http vs Spray performance

I tried to repeat this benchmark and would be glad to see comments to results I got. Tested porjects: gists from original post with the following versions: akka-http, 2.4.11 vs spray, 1.3.1 (akka - 2.3.6). In both cases scala 2.11.8, jvm 8. The tests were done on AWS machine of c4.2xlarge t

Re: [akka-user] Re: Akka http vs Spray performance

Hi Olga, establishing a connection is a very expensive operation, which is why all modern clients/browsers reuse them for multiple requests. The ab tool needs the -k switch to enable this behavior. Regards, Roland Sent from my iPhone > On 5 Oct 2016, at 01:32, Olga Gorun wrote: > > > I tr

Re: [akka-user] Re: Akka http vs Spray performance

Hi rkurn, Thank you for reply. You are right. keep-alive makes the difference. I updated in google spreadshit. On Wednesday, October 5, 2016 at 8:47:54 AM UTC+3, rkuhn wrote: > > Hi Olga, > > establishing a connection is a very expensive operation, which is why all > modern clients/browsers reu

Re: [akka-user] Re: Akka http vs Spray performance

I continue playing with given example projects and see strange results. If I increase string length of static response from 7 to 2490 characters throughput is reduced to ~24K rps for both spray and akka-http. Does anybody else see such results? How can they be explained? On Wednesday, Octobe

Re: [akka-user] Re: Akka http vs Spray performance

garbadge collection I guess. also I didn't see if you've set Xms/Xmx you should set them equal. And also try the following: -XX:+UseNUMA -XX:+UseG1GC -XX:+AlwaysPreTouch -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled paramters, not all of them will be helpful, but you should try some of

Re: [akka-user] Re: Akka http vs Spray performance

Hi Christian. Thank you for response. I checked that equal Xms/Xmx both set to more than enough memory (4GB while used heap is not more than 1.5GB during load test with or without explicitly defined memory) don't influence results. I'll try other JVM settings you propose. But generally speakin

Re: [akka-user] Re: Akka http vs Spray performance

For more information, I give here versions I test with. ubuntu 14.04, scala 2.11.8, oracle jdk 1.8 akka-http: 2.4.11 spray: 1.3.1 with akka 2.3.6 On Thursday, October 6, 2016 at 10:26:48 PM UTC+3, Olga Gorun wrote: > > Hi Christian. Thank you for response. I checked that equal Xms/Xmx both > s

Re: [akka-user] Re: Akka http vs Spray performance

I added scalatra (scalatra 2.4.1 on embedded jetty) to tests set. Two testing tools from three (ab and weighttp) give me approximately the same results for all three frameworks in ~70MB/s throughput when I test long static result. So it is similar to network bandwidth saturation. On the other