Conversation
Lexdysia strikes again...
These hooks will be used to call rusage_self() in each thread before and after the thread runloop.
This benchmark measures how the recv backends handle high system loads.
On my system, this was
truesize=960 rcvbuf=212992 frames_per_iface=220
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
1 participant
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.
The backend I think candumpr will eventually use is the multishot io_uring backend, with batched receives.
After intermediate benchmarking, I added support for hardware timestamps and dropcount through the control message interface - but due to effort, only in the multishot backend. It still performs significantly better than the others, especially under high CPU load.