Won't the GIL really limit the performance of this?
(I say this all as a Rubyist who as seen these same problems on the Ruby side)
http://sourceforge.net/mailarchive/forum.php?thread_name=jja...
http://dabeaz.blogspot.com/2012/03/pycon-2012-followup.html
"In any case, the performance of threads is highly specific to the application at hand. You can't just take some benchmark from one of my GIL talks and extrapolate that out to a general statement about all Python thread programming. Personally, I find that Python threads have worked pretty well for most of the problems where I've used them. Of course your mileage might vary."
So.... maybe, it depends on what you are doing.
Personally I would have been happy to see ProcessingActor in pykka, maybe with 0mq for the ipc. That would be cool, but this looks useful nonetheless.
I've been using managers over TCP for use as an image cache (the program is essentially an image resizing proxy), and in my limited benchmarks, it's fast enough. Now, this isn't some real-time trading application, so maybe 0mq would squeeze something, but TCP/Unix sockets is probably fast enough for most purposes here.