Skip to content

[scheduling] Use ASAP/ALAP bounds in the SDC scheduler#4489

Draft
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_939372611
Draft

[scheduling] Use ASAP/ALAP bounds in the SDC scheduler#4489
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_939372611

Conversation

@copybara-service

Copy link
Copy Markdown

[scheduling] Use ASAP/ALAP bounds in the SDC scheduler

By providing tighter initial ranges for the cycle variables in the LP model, the solver saves (apparently significant) time. This also lets us use the ASAP scheduler to compute the minimum possible pipeline length, if we need it.

If the ASAP scheduler fails to converge (which is possible for complex constraints, but rare), we fall back to using the SDC scheduler directly.

@copybara-service copybara-service Bot force-pushed the test_939372611 branch 3 times, most recently from 85b4e35 to ac18912 Compare June 29, 2026 17:34
By providing tighter initial ranges for the cycle variables in the LP model, the solver saves (apparently significant) time. This also lets us use the ASAP scheduler to compute the minimum possible pipeline length, if we need it.

If the ASAP scheduler fails to converge (which is possible for complex constraints, but rare), we fall back to using the SDC scheduler directly.

PiperOrigin-RevId: 939372611
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant