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

slack-19.0: early backport of vtorc optimizations, pt. 1 #549

Closed
wants to merge 2 commits into from

Conversation

timvaillancourt
Copy link
Member

@timvaillancourt timvaillancourt commented Oct 31, 2024

Description

This PR is an early backport of these vtorc optimizations:

  1. Improve efficiency of vtorc topo calls  vitessio/vitess#17071
  2. Move to native sqlite3 queries vitessio/vitess#17124

Following some fixes of nits + merge upstream, I'll re-backport

Related Issue(s)

vitessio#17114

Checklist

  • "Backport to:" labels have been added if this change should be back-ported
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on the CI
  • Documentation was added or is not required

Deployment Notes

We don't have to support anything but sqlite3 here, so let's use the
proper sqlite syntax. This allows removing the find / replace logic and
regexp matching which reduces vtorc CPU usage significantly.

Signed-off-by: Dirkjan Bussink <[email protected]>
Copy link

Thanks for the contribution! Before we can merge this, we need @dbussink to sign the Salesforce Inc. Contributor License Agreement.

@github-actions github-actions bot added this to the v19.0.5 milestone Oct 31, 2024
Signed-off-by: Tim Vaillancourt <[email protected]>
@timvaillancourt timvaillancourt force-pushed the bp-vtorc-optimizations.slack-19.0 branch from 96e1617 to 38f8a6e Compare November 1, 2024 00:35
@timvaillancourt timvaillancourt deleted the bp-vtorc-optimizations.slack-19.0 branch November 1, 2024 00:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants