Add peers-aware PUSH/PULL throughput rows#278
Open
rgbkrk wants to merge 1 commit into
Open
Conversation
de13c64 to
564ea06
Compare
564ea06 to
1b1a8a0
Compare
1b1a8a0 to
12bdc84
Compare
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.
Summary
This creates a fresh benchmark-only PR inspired by the old #263 cloud-agent branch.
Changes:
throughput/push_pull/{transport}/peers={peers}/{size}rows for zmq.rs and libzmqpushpull-omqperf-suite profile that matches the OMQ PUSH/PULL peer and message-size gridpeers=8,size=8192PUSH/PULL rows in the standard profilescripts/run_perf_suite.pyto expand{peers}filters and avoid artifact collisions when a profile has multiple entries for the same bench targetNotes
This is measurement coverage only. It does not change socket behavior or claim a new performance result.
Validation