awslabs / awslabs/analytics-accelerator-s3
Configure and add self-hosted GitHub runners on EC2
- Dominant language
- Java
- Stars
- 72
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
### Tell us more about this new feature.
This is necessary to run JMH driven microbenchmarks
This is technically possible today, however for results to be meaningful and the runtime to be bound, we need these invoked inside in AWS Region that also hosts the benchmarking bucket.
The default GH runners run on VM with unpredictable locality and thus are unsuitable
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by reviewing the repository's GitHub Actions workflows and the JMH microbenchmark setup, then identify how the benchmarking bucket's AWS Region is configured. Determine the EC2 runner provisioning and workflow requirements, and consider the work complete when benchmarks run on a self-hosted runner in the bucket's Region with bounded runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions, java
- Domain
- ci-cd, cloud, devops, infrastructure, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100