Re:Node.js memory benchmark confirms V8's GC may not be read...
by hannesw on Wednesday September 29, 2010 @02:14PM
(#1740440)
Yes, --trace-gc shows about 10 Mark-sweeps per second, each taking around 13 ms (no compacts though as far as I could see). But are those ~15% spent in GC are enough to explain the performance?
[ Parent
| on HN ]
Re:Node.js memory benchmark confirms V8's GC may not be read...
by mraleph on Wednesday September 29, 2010 @02:30PM
(#1740521)
You were saying that V8 GC is failing here so I just explained why JSON.parse is especially bad for V8 GC.
Strictly speaking I am not even convinced that GC is bottleneck here. Only profiling can reveal the real bottleneck.
[I tried small experiment: used thirdparty pure-JS JSON parser instead of V8 JSON.parse --- that changed GC profile, but did not affect response time.]