00:00
2094
More
See all Show me
BFPG's videos
 

Credits

Likes

Tags

  • oxbow_lakes 1 year ago
    Tom: in your example, you only have 2 actor *instances*: the scalazReceiveActor and scalazSendActor. But then you say you are running on a thread pool with 50 threads. I think this gives the wrong impression that the actors must be handling messages non-sequentially. i.e. that:

    scalazReceiveActor ! socket.accept

    Can somehow handle multiple connections simultaneously. Of course, this is not the case: the program as designed has a massive unnecessary bottleneck around the receive actor
  •  
  • Tom Adams 1 year ago
    Ah, yeah, I see what you mean, it isn't processing concurrently, no. The socket.accept call is blocking, but once a connection comes in the socket is passed into the actor's mailbox. True that there is a bottleneck here as the receive actor is processing sequentially.

    I've tweaked the code now to get around this. Nice catch.
  •  
This conversation is missing your voice. Take five seconds to join Vimeo or log in.

Advertisement

About this video

MP4
00:34:54
  • 784x576, 279.67MB
  • Uploaded Wed December 08, 2010
  • Please join or log in to download

Statistics

Date Plays Comments
Totals 584 5 2
Feb 24th 0 0 0
Feb 23rd 2 0 0
Feb 22nd 2 0 0
Feb 21st 1 0 0
Feb 20th 1 0 0
Feb 19th 1 0 0
Feb 18th 0 0 0