-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix outputBytes/Rows/Batches stats for PartitionedOutput #8072
Conversation
✅ Deploy Preview for meta-velox canceled.
|
@mbasmanova has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
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.
@mbasmanova thanks for the fix!
taskId, i, pool(), eagerFlush_, [&](uint64_t bytes, uint64_t rows) { | ||
auto lockedStats = stats_.wlock(); | ||
lockedStats->addOutputVector(bytes, rows); | ||
})); |
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.
Is this ok to capture this in a lambda?
Could that lead to crashes when this gets destroyed and the callback called?
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 be Ok since all operations are synchronous.
30f9e31
to
5130665
Compare
@mbasmanova has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@mbasmanova merged this pull request in 0152a05. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
PartitionedOutput operator used to report outputBytes/Rows/Batches the same as
inputBytes/Rows/Batches. With this change it reports outputBytes as number of
serialized bytes, outputRows the same as inputRows and outputBatches as number
of serialized pages produced. This helps get an accurate picture while debugging
issues with Exchange.