aptos-core
aptos-core copied to clipboard
evenly distribute the txn ranges
Description
simple and robust. we can always increase the runner when necessary
Type of Change
- [ ] New feature
- [ ] Bug fix
- [ ] Breaking change
- [x] Performance improvement
- [ ] Refactoring
- [ ] Dependency update
- [ ] Documentation update
- [ ] Tests
Which Components or Systems Does This Change Impact?
- [ ] Validator Node
- [ ] Full Node (API, Indexer, etc.)
- [ ] Move/Aptos Virtual Machine
- [ ] Aptos Framework
- [ ] Aptos CLI/SDK
- [ ] Developer Infrastructure
- [x] Other (specify)
How Has This Been Tested?
https://github.com/aptos-labs/aptos-core/actions/runs/8897955533
the run failed due to incompatible changes instead of timeout
Key Areas to Review
Checklist
- [x] I have read and followed the CONTRIBUTING doc
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I identified and added all stakeholders and component owners affected by this change as reviewers
- [ ] I tested both happy and unhappy path of the functionality
- [ ] I have made corresponding changes to the documentation
⏱️ 121h 10m total CI duration on this PR
🚨 1 job on the last run was significantly faster/slower than expected
| Job | Duration | vs 7d avg | Delta |
|---|---|---|---|
| rust-targeted-unit-tests | 23m | 16m |
We are abandoning manual ranges? I think we had them because different periods in the history replays at dramatically different speed?
This issue is stale because it has been open 45 days with no activity. Remove the stale label, comment or push a commit - otherwise this will be closed in 15 days.