Fix excessive cpu usage in daq logging. - #69
Merged
brichards64 merged 2 commits intoAug 10, 2026
Merged
Conversation
Removed an unused poll item from the zmq::pollitem_t array.
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
3 participants
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.
In this case, the zmq::poll is testing the readiness of two channels, an input channel and an output channel.
The output channel is (almost) always ready, so the poll falls straight through, without the intended 1ms pause for thought.
In the case that the output channel is not ready (essentially if it's buffer is full), then the send code below fails silently anyway, negating the value of the poll completely.
By only polling the output channel, the CPU usage in the thread is reduced from 100% to 3%, which is kinder to users working on containers on laptops (my laptop is melting trying to run this code).