-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove fast_idle
and delay_exit
scheduler modes and related scheduling loop checks
#664
Conversation
This does not really affect performance in DLA-Future or in the future overhead test, but it simplifies the scheduling loop noticeably so I'd like to keep this change. The only open question is the same as #665 (comment), i.e. whether the scheduler mode enums should be renumbered. @biddisco? |
bors try |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Yes, renumbering the enums seems sensible
8f0875b
to
b2e6061
Compare
b2e6061
to
b5d852b
Compare
bors try |
tryBuild failed: |
bors merge |
Fifth of N PRs to try to improve performance in DLA-Future. This is one of the changes in main...disable-cruft-scheduler where we see up to 25% improvement in DLA-Future miniapps. This branch needs to be benchmarked to see if it makes a difference on its own.
One change that have in the
disable-cruft-scheduler
branch is to unconditionally enable stealing always. It may be worth checking if that makes a difference, though I suspect the effect may be small.