PlacementV2: Consolidate Placement into Scheduler #96
+418
−0
Conversation
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
Signed-off-by: Cassandra Coyle <[email protected]>
Signed-off-by: Cassandra Coyle <[email protected]>
Signed-off-by: Cassandra Coyle <[email protected]>
Signed-off-by: Cassandra Coyle <[email protected]>
Signed-off-by: Cassandra Coyle <[email protected]>
Signed-off-by: Cassandra Coyle <[email protected]>
Signed-off-by: Cassandra Coyle <[email protected]>
|
This seems like a hands-down win across the board. Consolidation of the older Placement table into the newer Scheduler looks like it'd (significantly) reduce network I/O, CPU and memory usage while benefiting from the robust performance improvements iterated over the last several releases to Scheduler. |
Member
|
Eligible voters: @dapr/maintainers-dapr |
| - After that, subsequent changes are per-type: only the affected types must pause, update, and resume. | ||
|
|
||
| Sidecar Startup vs steady-state | ||
| - On new stream: Scheduler sends LOCK(all) → UPDATE(full snapshot: all types, versions per type) → UNLOCK(all). |
There was a problem hiding this comment.
Do you think that this will raise the startup time for daprd hosting actors? or no since this was still happening in placement v1?
| This enforces soft stickiness: per‑type updates do not stop actors that still map to the local sidecar, which avoids | ||
| unnecessary churn and short global pauses. | ||
| So, during LOCK([T]) → UPDATE([T]) → UNLOCK([T]), only actors of types [T] that moved to a remote owner are drained and | ||
| all others continue running. No namespace‑wide drain. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Proposal to improve Actors and Workflows Reliability and Performance by consolidating Placement -> Scheduler