Remove ZeroMQ subscription threading - #683
Draft
dwsutherland wants to merge 1 commit into
Draft
Conversation
dwsutherland
force-pushed
the
remove-zeromq-sub-threads
branch
from
April 13, 2025 08:57
fa5f1bd to
f070b06
Compare
Member
|
See also #574 |
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
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.
Just fooling around with no-threading options for receiving ZeroMQ subscription data from the scheduler(s).
However, this seems quite responsive, so thought I'd post it.
I was testing whether the memory accumulation at the UIS was related to threading or not:
#682
Turns out threading is not a problem in this regard..
Check List
CONTRIBUTING.mdand added my name as a Code Contributor.setup.cfg(andconda-environment.ymlif present).?.?.xbranch.