WIP: Implement spatial index for resource placement#1974
Closed
WIP: Implement spatial index for resource placement#1974
Conversation
2cc62a3 to
fd10b06
Compare
- Add FunctionScalingConfig (min_fe=0, max_fe=2) to data model - Extend ResourcePlacementIndex with FE tracking (TrackedFE, idle tracking) - Create fe_scaler.rs with FEScalingPlan and FEScaler::compute_plan() - Add get_scaling_config() to InMemoryState
When an allocation completes and there are no pending runs for the same function, use the spatial index to find runs from other functions that could fit on this executor. This triggers vacuum/create cycle for FE reuse.
cff5f77 to
4828247
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Spatial index implemenation to make the scheduler faster when there are too many function runs pending and new executors join