Brian, I for one can't wait for spidermonkey to bring threading back again. We are still stuck on spidermonkey 1.8.3+ until this comes back in style again.
The biggest problem we have right now is stop the world GC. All the threads must wait for GC to complete. We can have between 100 and 500+ threads running JS at a time. If you can make it so that all threads aren't stuck waiting for GC that would be really awesome. That's the biggest problem we have. Multiple JSRuntimes help some but it would be nice to break this up a bit more. The use case is a web server with JS used in server pages. We have pool(s) of JSContexts. We compile scripts and functions only once and execute them many times. Session state is maintained via a "session global object" where pages can save things for later executions. Mike M. _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
