Replies: 2 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
I would also advise to minimize the activity of high priority processes, like network and audio stack, thus it would be better to have the network disabled and no audio output from any applications. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to cover here some suggestions how to benchmark an updated implementation.
The main enemy of this benchmark is noise. Something like +- 0.1 seems inevitable, sometimes even +. 0.2 in the total results might be attributed to noise.
How to reduce noise:
sudo mdutil -i off /
or set up an exception such that the js-framwork-benchmark folder is not indexed.How to measure an update:
Let's say you want to improve vanillajs (this would be a very welcome PR 😄 ).
cp -r frameworks/keyed/vanillajs frameworks/keyed/vanillajs-old
.npm run bench -- --framework keyed/vanillajs keyed/vanillajs-old
npm run results
and open http://localhost:8080/webdriver-ts-results/dist/index.htmlHow to improve measurement
Let's say you're focused on a specific benchmark like create rows:
npm run bench -- --count 25 --benchmark 01_ --framework keyed/vanillajs keyed/vanillajs-old
with increased number of samples. I can't do that for a full run, but to find out whether an update works this can improve statistical testing.Beta Was this translation helpful? Give feedback.
All reactions