Node.js and io.js – Very different in performance

Re:Node.js and io.js – Very different in performance by mschoebel on Monday January 19, 2015 @02:07PM (#8913439)

Very interesting. After reading your comment, I tried allocating another Uint8Array and keeping it allocated throughout the entire test as a workaround for the issue you mentioned. Time for Node.js was unchanged, but io.js was down to about 5.5s now. Almost the same time as Node. Only about 10% slower.

The same happens when I use the --nouse-osr parameter that you mentioned.

[ Parent | on HN ]

Re:Node.js and io.js – Very different in performance by mraleph on Monday January 19, 2015 @02:14PM (#8913475)

Is it 10% slower even if you keep array alive and apply --nouse-osr (to both node.js and io.js)?

On my machine results are fluctuating within the same ballpark (though I am on Linux and benchmarking 64-bit builds).

[ Parent | on HN ]

Re:Node.js and io.js – Very different in performance by mschoebel on Monday January 19, 2015 @03:07PM (#8913757)

Ok, I hadn't tested with both before. Keeping the array alive and using --nouse-osr makes io.js only 2.3% slower than my original measurement for Node 0.10.35. Median of 5058ms.

And Node 0.10.35 shows basically the same results as before. I see less than 1% difference. Maybe just random fluctuation. Even if not. 1% is irrelevant.

[ Parent | on HN ]