Hacker News Reader

I'm always impressed by some of the optimisations they find: 0aa403b649 improves readDouble/readFloat in buffers by 200-800% simply by...moving the code to plain javascript binary operations instead of the C++ runtime.

View on HN

My understanding is that transitions between C++ runtime and JS context are relatively expensive.

What generates that improvement percent confidences that was included in that commit?

Yeah, could be that you see 200% improvement on first call and then proceed to suffer 2000% slowdown unless this is benchmarked properly.

Given the context it's likely the other way around

Nobody really cares if your 1 call is 20x slower though. Much better to make it 2x faster when there's 100 calls

I was talkiing about the tooling that generated the output, but this is a valid point too. Still want to know what the tooling is.

They probably just timed execution with a few thousand samples and compared results. Nothing too fancy either way, I think.

Reply on news.ycombinator.com