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
Ah, and one more thought: have we considered any statistical analysis that would look for multi-modal distributions (and warn, at least)? If we see that e.g. half of all runs of a benchmark run in 0.3s and half in 0.5s, and the distribution looks like the sum of two Gaussians, it may be better to warn the user "please check settings X, Y, Z; you seem to be alternating between two different configurations randomly" than to just present a mean of 0.4s with some wide variance, while the latter makes more sense if we just have a single Gaussian with truly random noise.
I don't really trust myself to implement Shapiro-Wilk myself, but I whipped up this script in R that checks the normality of count for each (arch, engine, wasm, phase, event) grouping:
So far, even when the benchmark results' distributions are definitely not bi-modal, they still aren't normal. Nor is the log of those results normal.
I think this technically invalidates the results of our t-test / effect size analyses, since these things assume that the data is normally distributed...
From #138:
We can use the Shapiro-Wilk test to determine normality: https://en.wikipedia.org/wiki/Shapiro%E2%80%93Wilk_test
The text was updated successfully, but these errors were encountered: