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.

Sign up for GitHub

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

Update continuous-profiling.md #8706

Merged
merged 1 commit into from
May 30, 2022
Merged

Update continuous-profiling.md #8706

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 2 additions & 5 deletions dashboard/continuous-profiling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,15 +21,12 @@ Continuous Profiling is an enhanced feature of [Manual Profiling](/dashboard/das
- Manual Profiling can only be used to analyze current occurring problems, while Continuous Profiling can be used to analyze both the current and historical problems.
- Manual Profiling allows to collect specific performance data for specific instances, while Continuous Profiling collects all performance data for all instances.
- Continuous Profiling stores more performance data, therefore it takes up more disk space.
- Continuous Profiling currently does not collect performance data from TiFlash due to the impact to the stability when profiling is performed frequently.

## Supported performance data

All performance data in [Manual Profiling](/dashboard/dashboard-profiling.md#supported-performance-data) is collected except for TiFlash CPU data, which is not collected due to stability reasons.
All performance data in [Manual Profiling](/dashboard/dashboard-profiling.md#supported-performance-data) is collected.

- CPU: The CPU overhead of each internal function on TiDB, TiKV and PD instances

> The CPU overhead of TiKV instances is currently not supported in ARM architecture.
- CPU: The CPU overhead of each internal function on TiDB, TiKV, TiFlash, and PD instances

- Heap: The memory consumption of each internal function on TiDB and PD instances

Expand Down