2 ms·
Two things I'd check first: 1. The benchmarks make servers generate a huge number of objects, so maybe, the GC is under too much pressure. 2. Another possibil
by 1st1 10y ago
Two things I'd check first:
1. The benchmarks make servers generate a huge number of objects, so maybe, the GC is under too much pressure.
2. Another possibility is that the v8 JIT can't optimize some JS code in nodejs, or does a poor job.
That said, only careful profiling can answer your question :)
- geekuillaume 10y agoI would be interested in seeing the performance difference in NodeJS TCP echo benchmark by using piping instead of reading/writing manually: socket.pipe(socket);