Great news, looking forward to the future. I have found at least one example of similiar work but I am not sure how legit it is (it is not open source) http://nodejx.com/ - they claim they do multi-threading seamlessly. I would not trust their binary release to try it though.
On Wednesday, January 29, 2014 4:06:40 AM UTC+1, Timothy J Fontaine wrote: > > There is actually room with some of the features from upcoming v8 that > opens the possibility of running VM contexts in threads relatively safely, > though I'm not sure if we'd ever support that as a mechanism to extend > cluster. > > But the idea of being able to identify cpu bound javascript and run it in > a background thread as a first class feature is a very interesting concept > that I'm not ready to give up on. > > That being said, most workloads are decidedly not cpu bound. > > Exactly, Start time is probably the worst (starting 4 workers take up 400ms here) 15 mb may be quite a lot for example on embedded platforms and does not seem very elegant to take up that much ram for simple tasks. On Wednesday, January 29, 2014 4:22:27 AM UTC+1, Arunoda Susiripala wrote: > > There is a notable difference between thread va child process. Threads are > much light weight. Child processes take more time to initalize and take > more mem.(~15 mb min in node) Regards, Damian -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
