-
Notifications
You must be signed in to change notification settings - Fork 409
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
Add a heavy restore to test pagestorage restore speed #4896
Add a heavy restore to test pagestorage restore speed #4896
Conversation
* add threads metrics * add threads metrics Signed-off-by: bestwoody <bestwoody@163.com> * format Signed-off-by: bestwoody <bestwoody@163.com> * update threadpool into thread_pool Signed-off-by: bestwoody <bestwoody@163.com> * UPDATE_CUR_AND_MAX_METRIC Signed-off-by: bestwoody <bestwoody@163.com> * refine include Signed-off-by: bestwoody <bestwoody@163.com>
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
|
||
restore_stop_watch.start(); | ||
// restore | ||
initPageStorage(config, name()); |
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.
I think the restore time should not include the traverse time.
ps->traverse([&num_of_pages](const DB::Page & page) { |
@jiaqizho: PR needs rebase. 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 kubernetes/test-infra repository. |
i don't know what happend... |
What problem does this PR solve?
Issue Number: ref #3594
Problem Summary:
What is changed and how it works?
HeavyRestore
to test the restore time.Check List
Tests
Side effects
Documentation
Release note