4 ms·
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 plai
by rf15 9y ago
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.
- coolspot 9y agoMy understanding is that transitions between C++ runtime and JS context are relatively expensive.
- Something1234 9y agoWhat generates that improvement percent confidences that was included in that commit?
- dingdingdang 9y agoYeah, could be that you see 200% improvement on first call and then proceed to suffer 2000% slowdown unless this is benchmarked properly.
- __s 9y agoGiven 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
- Something1234 9y agoI was talkiing about the tooling that generated the output, but this is a valid point too. Still want to know what the tooling is.
- rf15 9y agoThey probably just timed execution with a few thousand samples and compared results. Nothing too fancy either way, I think.