4 ms·
Fast Fact: due to a v8 bug, a Node.js process currently only supports a max of 1.9gb of RAM http://code.google.com/p/v8/issues/detail?id=847 http://code.google
by nestlequ1k 16y ago
Fast Fact: due to a v8 bug, a Node.js process currently only supports a max of 1.9gb of RAM
http://code.google.com/p/v8/issues/detail?id=847 http://code.google.com/p/v8/issues/detail?id=847
- EGreg 16y agoThat's fine if you are running a 16-core machine with 16GB of ram, isn't it? Just have one Node.js process per core.
- nestlequ1k 16y agoYep, easy enough to workaround. Seems like a needless limitation however. Would be nice if someone on node.js core (or v8 team at google) would try to fix that bug. Also wonder what other bugs are going to emerge as a result of trying to use a client side app on the server.
- johnm 16y agoDo note clearly that V8's garbage collector is fairly slow (think old Java GC) so having more instances of node with smaller heaps is a good idea anyways.
- EGreg 16y agoArgh, I was afraid of that. Can we have something that is a hybrid of refcounting and stop-the-world GC? I read some nice academic paper a few years ago about how people made a GC that combined the benefits of refcounting and stop the world.
- johnm 16y agoDepending on your workload, 1 node per 2 cores is a better rule of thumb. Also, split the networking across multiple NICs.