I haven't taken it up to tens of thousands of processes, but here's my pet 
project:

https://github.com/tristanls/anodejs

It naively uses process.nextTick for sending a message, which negatively 
affects performance (the correct answer is an optimisation based on what 
node.js release you have that would process an x number of messages per 
tick and then yield via process.nextTick). Also, unlike the drama that 
stagas mentioned, this is only for local machine without remoting.

On Sunday, June 17, 2012 2:50:00 AM UTC-5, Paul Miller wrote:
>
> So, as you know, erlang is great because of this one.
>
> Are there any great actor model implementations currently that will allow 
> you to spawn tens of thousands of processes without bullshit?
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to