-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test(benchmark): support log stream appender #462
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
The current lint failure will be fixed soon:
|
05f590e
to
ea02918
Compare
763e20d
to
e6b68f9
Compare
Codecov ReportPatch coverage has no change and project coverage change:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## log_stream_appender #462 +/- ##
=======================================================
+ Coverage 62.66% 62.69% +0.03%
=======================================================
Files 133 133
Lines 18336 18336
=======================================================
+ Hits 11490 11496 +6
+ Misses 6271 6267 -4
+ Partials 575 573 -2 ☔ View full report in Codecov by Sentry. |
ea02918
to
f8a7676
Compare
e6b68f9
to
53b2258
Compare
This PR adds the `--pipeline-size` flag to the benchmark tool. It makes the benchmark test client use LogStreamAppender, which allows pipelined append requests. - No pipelined requests if the flag is zero (default value). - Use pipelined requests by using LogStreamAppender if the flag is greater than zero. The benchmark tool cannot support per-target level pipelined yet. Thus, if the `--pipeline-size` is greater than zero, all the log stream-specific targets will use LogStreamAppender.
Graphite rebased this pull request as part of a merge. |
What this PR does
This PR adds the
--pipeline-size
flag to the benchmark tool. It makes the benchmark test client use LogStreamAppender, which allows pipelined append requests.The benchmark tool cannot support per-target level pipelined yet. Thus, if the
--pipeline-size
is greater than zero, all the log stream-specific targets will use LogStreamAppender.