Skip to content

Conversation

@lukasz-stec
Copy link
Member

Previously, outputDataSize for tasks and stages was equal to the memory retained by the pages sent to the output operator, and not the actual number of bytes sent over the network. The latter is more useful, as it can be used to discover internal network bottlenecks.

Description

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( X) Release notes are required, with the following suggested text:

## Section
* Make the stage output in the explain analyze, display the actual size of data sent over the network

Previously, `outputDataSize` for tasks and stages was equal to the memory retained by the pages sent to the output operator, and not the actual number of bytes sent over the network. The latter is more useful, as it can be used to discover internal network bottlenecks.
@cla-bot cla-bot bot added the cla-signed label Dec 23, 2025
@lukasz-stec
Copy link
Member Author

It turns out FTE does not use createBufferResultResponse, so tracking there only won't work for this mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant