Thank you very much for your answer. Could you let me know what those showstoppers are? And I don't have any experience with Node and I'm not intending to build a web server either. Is Node easier to use than native V8 for parallelization?
Thank you. On Tuesday, February 23, 2016 at 1:31:55 PM UTC-5, mog...@syntheticsemantics.com wrote: > > I, too, looked at adding OpenMP to v8 but there are several showstoppers > to adding parallelism *inside* v8. My solution was to add shared, > persistent objects as a native addon, and fork multiple instances of Node > for concurrency. > > The native addon prevents this from being used in browsers, but this > approach works embedded in systems with POSIX-like shared memory: EMS.js > home page <http://syntheticsemantics.com/EMS.js/>, GitHub > <https://github.com/SyntheticSemantics/ems> > > -J > > > On Monday, February 22, 2016 at 11:34:38 PM UTC-8, Tiny Wings wrote: >> >> About my question: >> This is actually not really much about parallelization; this is rather >> about how to do launch multiple threads in multiple cores within a >> javascript program and make them communicate when needed. >> > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
