feat: partition by mem & node latency #330
Draft
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.
Pull Request: Add Partitioning Strategy Flag with Latency-Aware Default
Description
Feature Added
--partitioning-strategy
CLI flag inmain.py
to allow selection between partitioning strategies.latency_aware
as the default partitioning strategy.Implementation Details
LatencyAwarePartitioningStrategy
alongside existing strategies.main.py
to parse the new--partitioning-strategy
flag.StandardNode
initialization to accept the chosen partitioning strategy.Testing
TestLatencyAwarePartitioningStrategy
intests/test_latency_aware_partitioning.py
to validate the new strategy.Additional Changes
node_service_pb2.py
andnode_service_pb2_grpc.py
to reflect.proto
updates.Usage
Default (Latency-Aware)