Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: guidelines for interpreting R^2 and stddev #106

Open
rrnewton opened this issue Jun 9, 2016 · 1 comment
Open

Documentation: guidelines for interpreting R^2 and stddev #106

rrnewton opened this issue Jun 9, 2016 · 1 comment

Comments

@rrnewton
Copy link
Member

rrnewton commented Jun 9, 2016

In running the ~2000 criterion benchmarks currently on stackage, we've run into the problem that some of them are clearly nonlinear.

We are trying to develop a data cleaning step which will throw these out before comparing two different runs of the full benchmark set. Once we find good thresholds, I would like to put some guidelines together to share these with criterion users.

This goes along with other documentation updates, e.g. #92 and #95.

CC @RyanGlScott @vollmerm

@ocramz
Copy link
Contributor

ocramz commented Mar 27, 2018

@rrnewton almost two years late, but I wonder how did you proceed with your data cleaning step? Rather than throwing performance datasets away it would be very instructive if these were publicly available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants