Revise the typo.
When I send 300, 000 message from one actor to another (all local actors),
more than 90% time of the source actor is spent in
Dispatcher.registerForExecution(), inside it, there is call
executorService.execute(mbox)
The Mailbox.run() logic looks like this: It will first try
registerForExecution has to be called for every message.
See the link I sent for both benchmark numbers and configuration for
throughput.
On Mon, Aug 18, 2014 at 4:25 PM, Sean Zhong clock...@gmail.com wrote:
Revise the typo.
When I send 300, 000 message from one actor to another (all local
I think there is a difference.
The benchmark you showed have no flow control. the receiver actor mailbox
will always have message. So, Mailbox.run() will only resubmit itself when
throughput is met(1024 in the test case).
So, take the throughput number from the benchmark 8,189,290 ops/s,
On Mon, Aug 18, 2014 at 5:12 PM, Sean Zhong clock...@gmail.com wrote:
I think there is a difference.
The benchmark you showed have no flow control. the receiver actor mailbox
will always have message. So, Mailbox.run() will only resubmit itself when
throughput is met(1024 in the test case).