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

Benchmarks in CI produce erroneous results #1793

Closed
Trott opened this issue Apr 28, 2019 · 6 comments
Closed

Benchmarks in CI produce erroneous results #1793

Trott opened this issue Apr 28, 2019 · 6 comments

Comments

@Trott
Copy link
Member

Trott commented Apr 28, 2019

Running benchmark CI jobs using PRs that only change the README file, I've found at least two that consistently report significant differences. I am not able to reproduce these erroneous results locally. Something is wrong with the benchmark CI setup, but I have no idea what.

Ref: nodejs/node#27380 (comment) and nodejs/node#27380 (comment)

Ref: nodejs/node#27081 (comment)

@github-actions
Copy link

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

@github-actions github-actions bot added the stale label May 25, 2020
@Trott Trott removed the stale label May 27, 2020
@github-actions
Copy link

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

@github-actions github-actions bot added the stale label Mar 24, 2021
@Trott
Copy link
Member Author

Trott commented Mar 26, 2021

Checking to see if timers benchmark is still affected: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/977/

(That's a PR doing a timers benchmark comparison using a PR that only changes a single .md file. So there should be no statistically significant difference in performance. Previously, I had consistently seen results indicating a statistically significant difference. That basically means we can't trust the benchmarks.)

@Trott
Copy link
Member Author

Trott commented Mar 26, 2021

Checking to see if timers benchmark is still affected: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/977/

(That's a PR doing a timers benchmark comparison using a PR that only changes a single .md file. So there should be no statistically significant difference in performance. Previously, I had consistently seen results indicating a statistically significant difference. That basically means we can't trust the benchmarks.)

I've also queued a dns benchmark for the same purpose: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/978/

@Trott Trott removed the stale label Mar 26, 2021
@Trott
Copy link
Member Author

Trott commented Mar 27, 2021

@Trott
Copy link
Member Author

Trott commented Mar 27, 2021

Looks good. Closing.

@Trott Trott closed this as completed Mar 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant