Skip to content

Add benchmark for the AgentWriter#842

Merged
kevingosse merged 2 commits into
masterfrom
kevin/benchmarks
Aug 14, 2020
Merged

Add benchmark for the AgentWriter#842
kevingosse merged 2 commits into
masterfrom
kevin/benchmarks

Conversation

@kevingosse

Copy link
Copy Markdown
Contributor

Added a benchmark for flushing traces for the agent, and disabled some background stuff for the span benchmarks.

Also added a way to disable the background task from the AgentWriter, to have more predictable results.

I had to mock the API requests and not actually send them, because I was getting throttled by the trace agent.

@kevingosse
kevingosse requested a review from a team as a code owner August 7, 2020 13:13

@tonyredondo tonyredondo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

public class SpanBenchmark
{
private static Tracer _tracer;
private static readonly Tracer Tracer;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a performance reason for this change?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

None whatsoever. It was just to please Resharper 😛

@kevingosse
kevingosse merged commit 36f0050 into master Aug 14, 2020
@kevingosse
kevingosse deleted the kevin/benchmarks branch August 14, 2020 15:20
@zacharycmontoya zacharycmontoya added this to the 1.19.2 milestone Aug 31, 2020
@zacharycmontoya zacharycmontoya added the area:benchmarks Benchmarks, throughput tests, Crank, Bombardier, etc label Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:benchmarks Benchmarks, throughput tests, Crank, Bombardier, etc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants