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

Jump to bottom

Allow disable OPTIMIZE TABLE queries in config file #3657

Closed
mattab opened this issue Jan 9, 2013 · 1 comment
Closed

Allow disable OPTIMIZE TABLE queries in config file #3657

mattab opened this issue Jan 9, 2013 · 1 comment
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone
1.10

Comments

@mattab
Copy link
Member

mattab commented Jan 9, 2013

Some very high traffic user reports that the OPTIMIZE TABLE query run at the end of the log purge, is causing trouble and sql queries queuing. We should at least allow to disable the OPTIMIZE queries via config file setting,

and the proper ultimate fix will be to have Piwik not require Mysql for tracking anymore SEE #3632
@mattab
Copy link
Member Author

mattab commented Jan 9, 2013

in [7738] fixing #3657 NEW config setting

; By default Piwik runs OPTIMIZE TABLE SQL queries to free spaces after deleting some data.
; If your Piwik tracks millions of pages, the OPTIMIZE TABLE queries might run for hours (seen in "SHOW FULL PROCESSLIST \g")
; so you can disable these special queries here:
enable_sql_optimize_queries = 1

@mattab mattab added this to the 1.10 - Piwik 1.10 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Milestone
1.10
Development

No branches or pull requests
1 participant
@mattab