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

Do not load table stats when booting vttablet. #15715

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

arthurschreiber
Copy link
Contributor

@arthurschreiber arthurschreiber commented Apr 15, 2024

Description

As part of the bootup process, vttablet reloads the schema engine, with table statistics information like table size, via the BaseShowTablesWithSizes query. This query is relatively expensive, but calling it once on vttablet bootup doesn't really seem much like an issue in production environments.

But in vtcombo, where a lot of vttablet instances are booted up on startup, all these BaseShowTablesWithSizes calls can add up, especially when there's a lot of tables / tablespaces.

In our CI system, where we use vtcombo, just the process of starting vtcombo on MySQL 8.0 takes 70 (!) seconds. On MySQL 5.7, it takes 26 seconds.

I already prepared a PR to halve the cost of running BaseShowTablesWithSizes on MySQL 8.0. But you know what's even better than halving the cost of this query? Not even running it in the first place!

This pull request proposes to skip the table size collection when booting up vttablet. This will improve the startup time, with virtually no negative side effect. The table statistics will be collected during the next regular schema engine reload interval.

This brings vtcombo bootup time in our CI system down to roughly 15 seconds, both on MySQL 5.7 and MySQL 8.0.

I'd really love to see this backported, because it's a massive performance improvement for everyone using vtcombo without any noticeable negative side effects, and it'd reduce the amount of patches I need to juggle until we get to a more recent version of Vitess. 😬

Related Issue(s)

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
Copy link
Contributor

vitess-bot bot commented Apr 15, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Apr 15, 2024
@arthurschreiber arthurschreiber added Type: Performance and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says labels Apr 15, 2024
@github-actions github-actions bot added this to the v20.0.0 milestone Apr 15, 2024
@deepthi deepthi added Component: VTCombo and removed NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Apr 17, 2024
@arthurschreiber arthurschreiber added Backport to: release-17.0 Needs to be back ported to release-17.0 Backport to: release-18.0 Needs to be back ported to release-18.0 Backport to: release-19.0 Needs to be back ported to release-19.0 Component: VTTablet labels Apr 19, 2024
@harshit-gangal
Copy link
Member

harshit-gangal commented Apr 25, 2024

Unit Tests are failing, those need to be fixed as the test expectation about the query have changed.

Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
@arthurschreiber arthurschreiber marked this pull request as draft April 25, 2024 22:28
Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
This was referenced Apr 29, 2024
@systay systay mentioned this pull request Apr 29, 2024
22 tasks
Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
…/do-not-load-stats-at-boot

Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
Copy link

codecov bot commented May 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.45%. Comparing base (f118ba2) to head (8e4b089).
Report is 58 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15715      +/-   ##
==========================================
+ Coverage   68.40%   68.45%   +0.05%     
==========================================
  Files        1556     1559       +3     
  Lines      195121   196515    +1394     
==========================================
+ Hits       133479   134532    +1053     
- Misses      61642    61983     +341     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport to: release-17.0 Needs to be back ported to release-17.0 Backport to: release-18.0 Needs to be back ported to release-18.0 Backport to: release-19.0 Needs to be back ported to release-19.0 Component: VTCombo Component: VTTablet NeedsIssue A linked issue is missing for this Pull Request Type: Performance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants