-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add Asia (Tokyo) Region Support & Parallel Benchmark Optimization #37
base: main
Are you sure you want to change the base?
Conversation
- Split into pre-warm and run-benchmarks jobs - Use matrix for regions and media types - Set max-parallel to 20 for GitHub Free tier
- Allows setting 1-20 parallel jobs, with 1 for sequential execution
Thanks for the PR, will take a look at this this week |
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.
Thanks for the PR! Just a couple minor comments.
strategy: | ||
fail-fast: false | ||
matrix: | ||
region: [sea, iad, cdg, nrt] |
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.
I think it's fine to parallelize region since those are separate runners, but parallelizing medium will put additional load on the runners which we know can affect the measurements. I'd suggest either keeping each medium as a serial task or having a separate max-parallel config that we can use to experimentally roll this out.
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.
Also, I turned up in Singapore (sin) vs Narita for broader Asia coverage.
Tokyo Region Support & Parallel Benchmark Optimization
Key Changes
Performance Enhancements
Workflow Optimization
BEFORE: Sequential execution
10m 30s
AFTER: 10 jobs running in parallel
2m 25s
Additional Notes
nrt
region is needed