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

Add Asia (Tokyo) Region Support & Parallel Benchmark Optimization #37

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

gunta
Copy link

@gunta gunta commented Oct 1, 2024

Tokyo Region Support & Parallel Benchmark Optimization

Key Changes

  • Introduced Asia (Tokyo) Region support
  • Implemented parallel benchmark workflow using matrix strategy
  • Optimized for multiple regions and media types
  • Restructured workflow into pre-warm and run-benchmarks jobs

Performance Enhancements

  • Set max-parallel to 10 (optimized for GitHub Free tier's 20 concurrent job limit)
  • Added retry mechanism for improved reliability

Workflow Optimization

BEFORE: Sequential execution 10m 30s

Screenshot 2024-10-01 at 11 03 08 PM

AFTER: 10 jobs running in parallel 2m 25s

Screenshot 2024-10-01 at 11 02 58 PM

Additional Notes

  • Deploy on Fly.io side for the nrt region is needed
  • Introduced max parallel jobs flag in benchmark workflow for future flexibility

- 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
@juberti juberti self-requested a review October 8, 2024 05:19
@juberti
Copy link
Contributor

juberti commented Oct 8, 2024

Thanks for the PR, will take a look at this this week

Copy link
Contributor

@juberti juberti left a 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]
Copy link
Contributor

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.

Copy link
Contributor

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.

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

Successfully merging this pull request may close these issues.

2 participants