statement-store: add statement-ops-bench for per-node RPC benchmarks#5
Open
alexggh wants to merge 3 commits into
Open
statement-store: add statement-ops-bench for per-node RPC benchmarks#5alexggh wants to merge 3 commits into
alexggh wants to merge 3 commits into
Conversation
Signed-off-by: Alexandru Gheorghe <alexandru.gheorghe@parity.io>
Signed-off-by: Alexandru Gheorghe <alexandru.gheorghe@parity.io>
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.
A new
statement-ops-benchbinary alongside the existingstatement-latency-benchinsubstrate/client/statement-store/statement-latency-bench/. While the latter measures aggregate ring-topology latency,statement-ops-benchtargets individual statement-store RPC operations on specific nodes via four subcommands:submit— measuresstatement_submitduration per endpoint, with optional--iteration-batchto pipeline submits in parallel on a single ws connection.propagation— measures submit→subscribe latency across every (submit, subscribe) pair, with separate ws connections per side.subscribe— measures per-node read latency viastatement_subscribeStatementwith a topic filter. With--topic, the bench deliberately assumes statement already exists in the store and reads time out cleanly if no matching statement is present.loop— periodically run the above; stops on--iterations,--duration-secs, or Ctrl-C.