Hi Sebastian,

First of all, we fixed a memory leak in the meantime that we discovered
(and what caused your benchmark to eventually fail). If connections are not
reused, we are still quite slow though, but it is relatively easy to gain
there 6-7x speedup, and we know exactly how (and I already have a PoC for
that) but we still cannot concentrate on these improvements. These will
come soon, though, so be patient please :)

As for the parallelism, I think you shound change the default-dispatcher
settings to have the max and min parallelism factor corresponding to your
cores. There are other optimizationstuff we will do soon, but we need to
fix bug first. You might also want to try a thread-pool-executor instead of
the fork-join-pool, streams tend to work faster with those.

-Endre

On Tue, Feb 2, 2016 at 4:09 PM, Sebastian Jastrzebski <[email protected]>
wrote:

> Hi Endre,
>
> Wow. Things do look a lot better with connection keepalive. The numbers
> went from 1k+ req/s to 40k+ req/s. That is certainly reassuring and a very
> impressive result. ;)
>
> Interestingly enough, one thing I still notice is that akka-http workload
> is not using all cores and revolves around 300% (using 3 out of 8 cores)
>  while the same test using spray backend saturates all of them (resulting
> is proportionally better numbers).
>
> See results below for both tests.
>
> Any thoughts on the cpu utilization?
>
> Thanks for all the help.
> -Sebastian
>
> *## Bench Results (akka-http)*
>
> Server Software:        akka-http/2.4.2-RC1
> Server Hostname:        localhost
> Server Port:            8000
>
> Document Path:          /v1/tweets
> Document Length:        96 bytes
>
> Concurrency Level:      100
> Time taken for tests:   23.685 seconds
> Complete requests:      1000000
> Failed requests:        0
> Keep-Alive requests:    1000000
> Total transferred:      257000000 bytes
> HTML transferred:       96000000 bytes
> Requests per second:    42220.09 [#/sec] (mean)
> Time per request:       2.369 [ms] (mean)
> Time per request:       0.024 [ms] (mean, across all concurrent requests)
> Transfer rate:          10596.25 [Kbytes/sec] received
>
>
> *## Bench Results (spray)*
>
> Server Software:        spray-can/1.3.3
> Server Hostname:        localhost
> Server Port:            8001
>
> Document Path:          /v1/tweets
> Document Length:        98 bytes
>
> Concurrency Level:      100
> Time taken for tests:   12.147 seconds
> Complete requests:      1000000
> Failed requests:        0
> Keep-Alive requests:    1000000
> Total transferred:      270000000 bytes
> HTML transferred:       98000000 bytes
> Requests per second:    82321.84 [#/sec] (mean)
> Time per request:       1.215 [ms] (mean)
> Time per request:       0.012 [ms] (mean, across all concurrent requests)
> Transfer rate:          21705.96 [Kbytes/sec] received
>
>
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to