AsyncLogger: enqueue logging operation instead of a log message #461
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.
My attempt to fix #460.
This approach fixes the underlying issue, but it affects the performance as well.
1) AsyncLoggerBenchmark
Original benchmarks of async logger are a little bit of cheating. Since they are basically measuring the
queue.offer
operation.Before (master branch):
After (fix branch):
2) Measure the cost of the
drain
operationI decided to measure the cost of the
drain
operation as well. I tweakedAsyncLoggerBenchmark
for this purpose:Before (master branch):
After (fix branch):