-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Use shared benchmark CI #105
Conversation
Benchmark Report✅ Pull request has no significant performance differences ✅ Click to expand comparison resultBenchmark check running at 2025-01-18 08:03:54 UTCThe baseline '105/merge' is EQUAL to the defined thresholds. Click to expand benchmark resultBaseline '105/merge'
ParserCollatingParserAllocations_256MiB
CollatingParserAllocations_Empty
CollatingParserCPUTime_256MiB
StreamingParserAllocations_256MiB
StreamingParserAllocations_Empty
StreamingParserCPUTime_256MiB
Serializer100xSerializerCPUTime_1024Parts
SerializerAllocations_1024Parts
SerializerAllocations_Empty
|
push: | ||
branches: [main] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added this. This helps with caching, as well as keeping a history of the benchmarks.
caches have branch-rules. meaning you can only retrieve a cache if it was saved by the current branch, OR the primary branch of the repo.
So the first run of a benchmark event in CI won't have a cache if we don't run benchmarks on push to main.
Though we could workaround this even without push to main. For example manually running the workflow on the main branch so it saves a base cache.
bfdb505
to
1c51ecd
Compare
.github/workflows/benchmark.yml
Outdated
benchmark: | ||
# If this is a pull-request related event, make sure this is a pr-approval event or someone has rerun the job. | ||
if: (startsWith(github.event_name, 'pull_request') != true) || (github.event.review.state == 'approved' || github.run_attempt > 1) | ||
uses: vapor/ci/.github/workflows/run-benchmark.yml@mmbm-benchmark |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to change @mmbm-benchmark
to @main
before merge
b009c93
to
31a839f
Compare
a7f07c7
to
fa0919f
Compare
echo "Previous exit code was: $EXIT_CODE" | ||
exit $EXIT_CODE | ||
benchmark: | ||
if: github.run_attempt > 1 || github.event.review.state == 'approved' || startsWith(github.event_name, 'pull_request') != true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keeping the if condition here ... should i move it to the reusable CI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No this should probably be in the reusable CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Disagree - different repos may not want to use the same conditions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm hard decision. We generally don't add the if condition to the reusable CI so I guess we can keep at that.
I can see it coming back to bite us in either case.
No description provided.