JActor Status: the good, the bad and the ugly

[William la Forge]

https://sourceforge.net/p/jactor/blog/2012/06/performance-the-good-the-bad-and-the-ugly/

JActor messaging throughput has dropped significantly, and this has got to be fixed. See the above link for details.

[Mark]

Can you not just roll back to a version where throughput was quicker and build back up from there?

Mark

On 29 June 2012 13:38, William la Forge <lafo...@gmail.com> wrote:

https://sourceforge.net/p/jactor/blog/2012/06/performance-the-good-the-bad-and-the-ugly/

JActor messaging throughput has dropped significantly, and this has got to be fixed. See the above link for details.

--
You received this message because you are subscribed to the Google Groups "AgileWikiDevelopers" group.
To post to this group, send email to agilewiki...@googlegroups.com.
To unsubscribe from this group, send email to agilewikidevelo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/agilewikidevelopers?hl=en.

[William la Forge]

I figured it out and it is not fixable.

It is slower because of a fix for exception handling. So messages between actors sharing the same mailbox are just a bit faster than messages between actors with different mailboxes. But if you want speed and the mailbox is shared, you can always just do a method call.

Messages passed between mailboxes are wrapped to track additional information. Now all messages are wrapped and all requests subclass Request. If we create a Response class and require all responses to subclass it, then we could eliminate the wrapper and its subsequent garbage collection. Perhaps that could be a part of JActor release 4.

Bill

[William la Forge]

See  https://github.com/laforge49/JActor/issues/35