Skip to content
New issue

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

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

Already on GitHub? # to your account

Weird discrepencies in performance results in latest backfill #24

Open
squeek502 opened this issue Jun 3, 2022 · 0 comments
Open

Weird discrepencies in performance results in latest backfill #24

squeek502 opened this issue Jun 3, 2022 · 0 comments

Comments

@squeek502
Copy link
Contributor

squeek502 commented Jun 3, 2022

The latest run of the backfill script seems to be reporting much lower wall clock/cpu instruction count/etc results for all the commits included in its run (the oldest commit included in the backfill was commit 0c1df96b17fcafdb0aa973dfcb1819929719d650, which is exactly where this performance difference is reported).

zig-fmt-jump

This is not a real performance difference, though, as the commit that is reported as the cause is unrelated to any of the current benchmarks. It also only affects certain benchmarks--some don't have any performance difference at this commit.

Really unsure what is causing this, but have noticed one thing:

  • Every affected benchmark (zig-fmt, ast-check-os, comptime-guid-parse, etc) uses a child process for their benchmark (that is, they call useChildProcess() in their setup fn). Any benchmark that doesn't use a child process does not have the same erroneous performance difference.
@squeek502 squeek502 changed the title Weird discrepencies in wall clock/instruction count/etc in latest backfill Weird discrepencies in performance results in latest backfill Jun 3, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant