Skip to content

Report connector provided read time as connector metric#10472

Merged
sopel39 merged 1 commit intotrinodb:masterfrom
starburstdata:ks/physical_read_time
Jan 11, 2022
Merged

Report connector provided read time as connector metric#10472
sopel39 merged 1 commit intotrinodb:masterfrom
starburstdata:ks/physical_read_time

Conversation

@sopel39
Copy link
Copy Markdown
Member

@sopel39 sopel39 commented Jan 5, 2022

Previously connector provided read time was added
to OperatorContext#addInputTiming which caused table scan
wall time to be accounted for twice.

@sopel39 sopel39 requested a review from findepi January 5, 2022 14:44
@cla-bot cla-bot bot added the cla-signed label Jan 5, 2022
@sopel39
Copy link
Copy Markdown
Member Author

sopel39 commented Jan 5, 2022

fyi @martint

@findepi findepi requested a review from losipiuk January 10, 2022 09:55
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not a big fan of using 0 as a special marker. Can we use OptionalLong. Or if maybe -1 so we use value which is out of domain for valid values?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will leave it as is. It's not a maker really, but rather skipping meaningless stat.
We do something similar for other things, e.g:
39f48d5

            if (node.isMaySkipOutputDuplicates()) {
                nodeOutput.appendDetailsLine("maySkipOutputDuplicates = %s", node.isMaySkipOutputDuplicates());
            }

If I used -1 then I would have to take care of it while doing addition (synchronization). Similaraly Optional would require some synchronization and locking.

Previously connector provided read time was added
to OperatorContext#addInputTiming which caused table scan
wall time to be accounted for twice.
@sopel39 sopel39 force-pushed the ks/physical_read_time branch from 4792b03 to b4d12e4 Compare January 11, 2022 13:48
@sopel39 sopel39 merged commit 3c7130b into trinodb:master Jan 11, 2022
@sopel39 sopel39 deleted the ks/physical_read_time branch January 11, 2022 17:07
@sopel39 sopel39 mentioned this pull request Jan 11, 2022
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.

4 participants