Empty Node Module Memory Usage #8938
Comments
I wonder if maybe this is some rampup time for some libs that are loading async in the background, or, if maybe this is libuv or other deps ramping up in the background? I ran these on Mac OSX using node v0.10.33 (stable) on system Darwin12.5.0 Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64 Output from simple test:
In the second test:
|
I left this running every 10 seconds for a good while to see if it was just a ramp up, but it still looks like it's just going and going and going: https://gist.github.com/netpoetica/4d16382c3cfbf6db0f58 - Mac OSX using node v0.10.33 (stable) on system Darwin12.5.0 Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64 Running the same test with Node v0.11.14: https://gist.github.com/netpoetica/1a0a6652fa6c22b76951 |
@netpoetica in your test with node v0.10.33, we can see some decreases, eg lines 1397 or 1758. |
in 0.11 there was no initial dip and then went up leaving a small increase later:
in 0.10 there was an initial dip for a little while (it decreased a bit), and then went up leaving a larger increase later but I do believe this test ran much longer:
|
This is almost certainly the result of (unavoidable!) garbage being generated by the timer subsystem. V8 will happily grow the heap until it trips the compaction heuristic. Here's a link covering some bits about the GC. You may try running with |
Hello Guys, Att, |
Unstoppable memory usage increase
Node is increasingly using RSS and Heap memory for doing nothing
My environment
How to reproduce problem
Just start an empty node module and log memory usage each seconds:
For better readability, let's use this instead:
Expected result
Memory usage should be constant
Actual result
Heap and RSS memory are increasing
My results:
The text was updated successfully, but these errors were encountered: