Load balance the test file timings across N workers instead of applying a bin packing algorithm #115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Targeting total runtime / partitions for bin capacity can lead to many scenarios where you have empty bins. This is not ideal for test partitioning because we want to distribute the tests across a specified number of workers as evenly as possible. Notably, we don't want to try to fill bins as full as possible leaving any empty.
Instead of bin packing, this problem more closely relates to load balancing. A simple "shortest queue first" approach works very well and ensures all partitions get tests (so long as there are more files than partitions). In this case, queue depth is the total runtime we've added so far.