Add end-to-end benchmarking #1178
Merged
Conversation
This file contains 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
|
@marcotc I think we're missing some methods on the new test for shutdown? |
|
@ericmustin, oops, it seems like I deleted a word from the original PR, fixed now 👍 |
ericmustin
approved these changes
Sep 18, 2020
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.
Add an end-to-end test to our benchmarking suite.
This test generated traces (ranging from 1 to 100 nested spans), sends them to the write, which sends it by HTTP to a locally running agent.
This benchmark exercises the exact same code path that host applications will perform.
With this benchmark we should be able to report on measurable, tracer-level gains performed when optimizations on a subset of the tracer.