windsock: fix ops instability #1360
Draft
Conversation
This file contains 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
rukai
force-pushed
the
windsock_fix_task_running
branch
from
99ad549 to
5c462fd
Compare
rukai
force-pushed
the
windsock_fix_task_running
branch
4 times, most recently
from
49faa4f to
b8f6080
Compare
rukai
force-pushed
the
windsock_fix_task_running
branch
from
b8f6080 to
1361676
Compare
This was referenced Feb 1, 2024
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.
This gives more stable results when no OPS cap is set, but when I cap the OPS the results jump significantly above the cap which is very wonky.
Leaving as a draft for a bit because I need to go on with some other work for a bit.