Comment #2 on issue 847 by diego.caravana: 1gb memory limit http://code.google.com/p/v8/issues/detail?id=847
Even if this can be acceptable in a web browser, IMHO it is not when dealing with server-side processes. In my case, I've been forced to suddenly stop my work (an experiment with real-time web) with node.js because it cannot handle more than ~140K websockets concurrent connections (and my target is quite higher). I'm sorry to say that I was surprised hitting this V8 limit (hey, it's a *Google* product! ;) ) and I wonder why the type of this issue in not "bug" and why it has a so low priority: does this mean that Google/V8 team has no strategic interest in making V8 a server-side tool capable to handle heaps bigger than 1GB (easy to reach, you know)?
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
