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.
I saw this crippling CPU on the scheduler for cases where there are many tasks queued (>250k). I haven't thoroughly tested this but I don't see the need to sort. I also believe there is no need to transition all at once since individual task chains would be processed before the next queued tasks anyhow, i.e. this should not affect ordering, I believe.
Generally, the sort does not truly help us here and we have to pop the heap for every task individually anyhow.