Repository navigation
sfqd-core: fix refundable queue scaling and release 1.2.0 - #25
Merged
Merged
Conversation
Keep long cancellation-heavy queues from monopolizing the scheduler lock. Preserve exact refund admission and dispatch behavior while bounding ordinary queue updates logarithmically.
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.
Long queues under REFUND_CANCELLED_COST make ordinary enqueue and cancellation scan queued work while holding the scheduler lock. Maintain exact live-cost sum/gcd aggregates in an AVL multiset and materialize tags at head promotion, reducing ordinary queue updates to O(log K) while preserving the existing admission domain, dispatch order, numeric budgets, public API, and charge-reserved default.
Add long-queue differential, aggregate, and cancellation-before-rebase regressions; expose queue length in JMH cancellation cycles; update complexity documentation and release metadata to 1.2.0. Local JMH reproduces the old queue-length scaling defect; application-specific throughput and deadline guarantees remain out of scope.
Validation passed locally: clean verify (130 core tests and 5 example tests); jcstress (182 configurations); benchmark profile and discovery; JavaDoc negative gate; two-build reproducibility for five artifacts; publication topology with an independent consumer. Maven Central publication and external consumer verification remain pending signing access and green CI.