Add RPC-count instrumentation harness for RPC load#719
Draft
konradkonrad wants to merge 1 commit into
Draft
Conversation
A JSON-RPC counting proxy sits between the tests and an ethclient/simulated backend and records how many times each method is invoked. Two tests use it to expose the RPC-call reduction of two optimization commits (B4 in medley/eventsyncer, S2 in keyperimpl/shutterservice/MultiEventSyncer) without touching production code. Test bodies only t.Log the counts, so the same source runs on both sides of the change and the numbers can be diffed by eye.
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.
A JSON-RPC counting proxy sits between the tests and an
ethclient/simulated backendand records how many times each method is invoked. Two tests use it to expose the RPC-call reduction of two optimization commits (B4 inmedley/eventsyncer, S2 inkeyperimpl/shutterservice/MultiEventSyncer) without touching production code. Test bodies onlyt.Logthe counts, so the same source runs on both sides of the change and the numbers can be diffed by eye.This is a utility for #717