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.
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
Refactor BatchLogProcessor #2494
Refactor BatchLogProcessor #2494
Changes from 3 commits
f040407
9c210b0
77dd3e8
e81c639
a599c1c
177abcf
7291998
5f56d1c
08687d1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 298 in opentelemetry-sdk/src/logs/log_processor.rs
Codecov / codecov/patch
opentelemetry-sdk/src/logs/log_processor.rs#L298
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we use
compare_exchange
instead ofswap
. This will avoid redundant writes if theexport_log_message_sent
is already true?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I used
swap
because it's less verbose. Note that bothswap
andcompare_exchange
need exclusive access to the cache line. More importantly, acompare_exchange
operation would need exclusive access even to perform the comparison.I pushed some new changes. I have added a new if check using atomic load to avoid aggressively calling
swap
. We would now callswap
only if the atomic load value returnedfalse
. Let me know what you think.Check warning on line 311 in opentelemetry-sdk/src/logs/log_processor.rs
Codecov / codecov/patch
opentelemetry-sdk/src/logs/log_processor.rs#L307-L311
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can get rid of
logs
vec and instead create a fresh array and pass its slice to export method.?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For using array, we need to know the size of the array beforehand which we don't because we don't know how many items are present in the channel. It might be less than
max_export_batch_size
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can allocate an array of max_export_batch_size, and slice it at the required length. Anyway, this is not a blocker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Always stack allocating a big array even to export very few logs seems wasteful.
What's the benefit of using an array instead of a
vec
here? We are reusing the samevec
for each export anyway so allocation isn't a concern.Check warning on line 447 in opentelemetry-sdk/src/logs/log_processor.rs
Codecov / codecov/patch
opentelemetry-sdk/src/logs/log_processor.rs#L447
Check warning on line 473 in opentelemetry-sdk/src/logs/log_processor.rs
Codecov / codecov/patch
opentelemetry-sdk/src/logs/log_processor.rs#L470-L473
Check warning on line 485 in opentelemetry-sdk/src/logs/log_processor.rs
Codecov / codecov/patch
opentelemetry-sdk/src/logs/log_processor.rs#L475-L485
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as flush - we need to ensure logs are continued to be exported until it finishes all logs received upto the point shutdown was invoked.
Check warning on line 530 in opentelemetry-sdk/src/logs/log_processor.rs
Codecov / codecov/patch
opentelemetry-sdk/src/logs/log_processor.rs#L528-L530
Check warning on line 534 in opentelemetry-sdk/src/logs/log_processor.rs
Codecov / codecov/patch
opentelemetry-sdk/src/logs/log_processor.rs#L533-L534