chore: run benchmarks in non-PERF mode #440
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #439
Unfortunately, since I can't figure out how to get
PERF=1
mode running when Tachometer builds the remote branch, we should just disable it everywhere. It gives additional instrumentation, which may distort the benchmark since we're not technically comparing apples to apples. The downside is that it's harder to debug the benchmarks, but it's better to have accurate benchmarks than debuggable ones (for now).