Repository navigation
perf: give the continuity stage 2.5 s, bounded by the deadline - #178
Merged
Merged
Conversation
With the gate on the cost stage clock, 45 % of the split requests that used to be skipped now run the stage, and every one of them ended at the 1 s cap with nothing kept. The split ends around 5 to 6 s of the 10 s limit, so 2.5 s fits inside what is left; _continuity_clock already bounds it by the deadline. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Oct 4, 2026
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
1 participant
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.
Follow-up to #177 from the first hour of revision 48 in production. The cost-clock gate lets the continuity stage run on the split requests whose cost stage finished under a second, 45 % of the ones it used to skip, and every one of those ended as
MILP … unusedat the 1 s cap. The stored #170 request needs 1.1 s to return its merged schedule, production models are larger.CONTINUITY_TIME_LIMITgoes from 1 s to 2.5 s. It is both the cap on the candidate and the solve time above which the stage is not tried, and_continuity_clockalready bounds it by the request deadline. Split requests end around 5 to 6 s of the 10 s limit, so the extra 1.5 s sits inside the clock that is left. Joint-path solves that took up to 2.5 s now also get the stage; on revision 47 those were the ones producing theimprovedlines, so the cost there is bounded by what the stage finds.To judge:
continuityoutcomes onpath == 'split'by revision, improved against unused, and split elapsed p99 against the 10 s limit.🤖 Generated with Claude Code