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

Optimise tables separately #18032

Merged
merged 2 commits into from Sep 21, 2021
Merged

Optimise tables separately #18032

merged 2 commits into from Sep 21, 2021

Conversation

bx80
Copy link
Contributor

@bx80 bx80 commented Sep 20, 2021

Description:

Fixes #14719

Rather than optimizing all tables in a single query, the optimize tables task will run each table optimization separately to allow breathing space for replicating servers.

Review

@bx80 bx80 added the Needs Review PRs that need a code review label Sep 20, 2021
core/Db.php Outdated Show resolved Hide resolved
Co-authored-by: Stefan Giehl <stefan@matomo.org>
@tsteur tsteur added this to the 4.5.0 milestone Sep 21, 2021
@tsteur tsteur merged commit ba2170d into 4.x-dev Sep 21, 2021
@tsteur tsteur deleted the m-14719-optimize-tables-separately branch September 21, 2021 01:17
@justinvelluppillai justinvelluppillai added the not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. label Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Review PRs that need a code review not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Run OPTIMIZE TABLE on each table in a separate SQL query to work better with replication
4 participants