Skip to content
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

Enrich the infomation about FullTableScan operator of TiFlash in explain analyze #6314

Merged
merged 30 commits into from
Nov 28, 2022

Conversation

hongyunyan
Copy link
Contributor

@hongyunyan hongyunyan commented Nov 15, 2022

What problem does this PR solve?

Issue Number: close #5926

Problem Summary:
Enrich the information about FullTableScan operator of TiFlash in explain analyze.

New information includes:

  • the count of packs read in the query
  • the count of packs skipped in the query
  • the count of rows read in the query
  • the count of rows skipped in the query
  • the time of reading related dmfile in the query
  • the time of loading the related rough set index in the query
  • the time of creating snapshot in the query

What is changed and how it works?

  • New class TableScanContext for the metrics of storage level
  • Enrich the Execution Summary based on the metrics in TableScanContext
  • Collect the metrics in TableScanContext and support gather the TableScanContext in ExecutionSummaryCollector

Related PRs:
pingcap/tipb#278 merged first)
pingcap/tidb#39216

Examples:
image

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
    create table and insert 50w data, and then run the sql to check the metrics.
  • No code

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

None

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Nov 15, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • SeaRise
  • breezewish

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 15, 2022
@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 18, 2022
@ti-chi-bot ti-chi-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 21, 2022
@hongyunyan hongyunyan changed the title WIP: Enrich the infomation in explain analyze Enrich the infomation in explain analyze Nov 21, 2022
@ti-chi-bot ti-chi-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 21, 2022
@hongyunyan hongyunyan requested review from breezewish and JaySon-Huang and removed request for breezewish November 21, 2022 05:05
@hongyunyan hongyunyan changed the title Enrich the infomation in explain analyze Enrich the infomation about FullTableScan operator of TiFlash in explain analyze Nov 21, 2022
@hongyunyan
Copy link
Contributor Author

/cc @SeaRise

@ti-chi-bot ti-chi-bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Nov 23, 2022
@hongyunyan
Copy link
Contributor Author

/run-all-tests

Copy link
Member

@breezewish breezewish left a comment

Choose a reason for hiding this comment

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

The rest LGTM

dbms/src/Flash/Coprocessor/DAGStorageInterpreter.cpp Outdated Show resolved Hide resolved
dbms/src/Flash/Coprocessor/ExecutionSummaryCollector.cpp Outdated Show resolved Hide resolved
dbms/src/Storages/DeltaMerge/DMContext.h Outdated Show resolved Hide resolved
dbms/src/Storages/DeltaMerge/DMContext.h Outdated Show resolved Hide resolved
dbms/src/Storages/DeltaMerge/File/DMFileReader.h Outdated Show resolved Hide resolved
dbms/src/Storages/DeltaMerge/ScanContext.h Show resolved Hide resolved
dbms/src/Storages/DeltaMerge/ScanContext.h Outdated Show resolved Hide resolved
dbms/src/Storages/StorageDeltaMerge.cpp Outdated Show resolved Hide resolved
@hongyunyan
Copy link
Contributor Author

/run-all-tests

@hongyunyan
Copy link
Contributor Author

/run-all-tests

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Nov 25, 2022
@hongyunyan
Copy link
Contributor Author

/run-all-tests

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Nov 28, 2022
@hongyunyan
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

@hongyunyan: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 6d2ee5a

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Nov 28, 2022
@ti-chi-bot ti-chi-bot merged commit 6811b93 into pingcap:master Nov 28, 2022
Copy link
Contributor

@JaySon-Huang JaySon-Huang left a comment

Choose a reason for hiding this comment

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

Sorry for the late reply. I think we can avoid the new StorageDeltaMerge::read interface

Comment on lines +784 to +791
const auto & scan_context = dag_context.scan_context_map.at(table_scan.getTableScanExecutorID());

// We want to collect performance metrics in storage level, thus we need read with scan_context here.
// while IStorage::read() can't support it, and only StorageDeltaMerge support to read with scan_context to collect the information.
// Thus, storage must cast to StorageDeltaMergePtr here to call the corresponding read() function.
StorageDeltaMergePtr delta_merge_storage = std::dynamic_pointer_cast<StorageDeltaMerge>(storage);
RUNTIME_CHECK_MSG(delta_merge_storage != nullptr, "delta_merge_storage which cast from storage is null");
pipeline.streams = delta_merge_storage->read(required_columns, query_info, context, from_stage, max_block_size, max_streams, scan_context);
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we can put scan_context into qeury_info.mvcc_query_info to avoid creating another StorageDeltaMerge::read interface

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

More details about table scan in the explain analyze output
5 participants