Hi Reid,
currently I don’t have the bandwidth to fully understand what you are doing,
but the numbers you quote here sound suspiciously like the “ping–pong problem”:
if your thread pool is too big and messages always hop threads even if they
should not, then you will incur the full CPU wake-up
Hi Roland,
On Feb 24, 2015, at 5:23 AM, Roland Kuhn goo...@rkuhn.info wrote:
Hi Reid,
currently I don’t have the bandwidth to fully understand what you are doing,
I appreciate any response at all. Thank you!
but the numbers you quote here sound suspiciously like the “ping–pong
Hi Adam,
On Feb 23, 2015, at 4:58 PM, Adam adamho...@gmail.com wrote:
I believe 50M messages per second on a single machine was mainly an example
for scaling up. See the kind of machine that was used for it
I believe 50M messages per second on a single machine was mainly an example
for scaling up. See the kind of machine that was used for it
http://letitcrash.com/post/20397701710/50-million-messages-per-second-on-a-single
.
Anyway, have you tried doing the same analysis on the legacy driver?
It
Hello Reid,
It seems you’re asking about performance of *akka-streams* not of *akka-io*,
as seen by your mention of outgoingConnection - do not confuse these two
modules.
The current performance of akka-streams has not been tuned at all, we know
and have been quite vocal about it during it's
Hi Adam,
Comments inline …
On Feb 23, 2015, at 2:19 AM, Adam adamho...@gmail.com wrote:
I think the OS you're using matters a lot for this sort of test. Hopefully
it's not windows…
No, it is Mac OSX Yosemite 10.10.2. I realize that absolute measurements on
this kind of machine are not
