You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.
This issue is for discussion on the existing micro-benchmarks, what we do in order to improve and get the running again.
One suggestion so far is that we make sure they print and display time for single iteration (how many us to complete) were the time is both the wall time as well as the cycles used.
We also discussed coming up with a list of additional micro benchmarks that we might want to add
The text was updated successfully, but these errors were encountered:
IMO the most reliable things to micro-benchmark are native calls (e.g. Buffer#slice()). Will definitely want to exclude micro calls (e.g. Buffer#writeUInt8()).
May want to consider implementing some for the complex JS paths (e.g. several streams paths).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is for discussion on the existing micro-benchmarks, what we do in order to improve and get the running again.
One suggestion so far is that we make sure they print and display time for single iteration (how many us to complete) were the time is both the wall time as well as the cycles used.
We also discussed coming up with a list of additional micro benchmarks that we might want to add
The text was updated successfully, but these errors were encountered: