mirror of
https://github.com/nodejs/node.git
synced 2024-11-30 07:27:22 +01:00
570e4be932
In zlibBuffer(), don't wait for the garbage collector to reclaim the zlib memory
but release it manually. Reduces memory consumption by a factor of 10 or more
with some workloads.
Test case:
function f() {
require('zlib').deflate('xxx', g);
}
function g() {
setTimeout(f, 5);
}
f();
Observe RSS memory usage with and without this commit. After 10,000 iterations,
RSS stabilizes at ~35 MB with this commit. Without, RSS is over 300 MB and keeps
growing.
Cause: whenever the JS object heap hits the high-water mark, the V8 GC sweeps
it clean, then tries to grow it in order to avoid more sweeps in the near
future. Rule of thumb: the bigger the JS heap, the lazier the GC can be.
A side effect of a bigger heap is that objects now live longer. This is harmless
in general but it affects zlib context objects because those are tied to large
buffers that live outside the JS heap, on the order of 16K per context object.
Ergo, don't wait for the GC to reclaim the memory - it may take a long time.
Fixes #4172.
|
||
|---|---|---|
| .. | ||
| _debugger.js | ||
| _linklist.js | ||
| assert.js | ||
| buffer_ieee754.js | ||
| buffer.js | ||
| child_process.js | ||
| cluster.js | ||
| console.js | ||
| constants.js | ||
| crypto.js | ||
| dgram.js | ||
| dns.js | ||
| domain.js | ||
| events.js | ||
| freelist.js | ||
| fs.js | ||
| http.js | ||
| https.js | ||
| module.js | ||
| net.js | ||
| os.js | ||
| path.js | ||
| punycode.js | ||
| querystring.js | ||
| readline.js | ||
| repl.js | ||
| stream.js | ||
| string_decoder.js | ||
| sys.js | ||
| timers.js | ||
| tls.js | ||
| tty.js | ||
| url.js | ||
| util.js | ||
| vm.js | ||
| zlib.js | ||