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
Large Mysql Database and running Piwik at scale: challenges #6759
Comments
Source: mysql performance blog These tools are out there for years, yet it appears that still many MySQL users are not aware of them. Let me just name here pt-online-schema-change from Percona Toolkit, oak-online-alter-table from Openark Kit or Facebook OSC. |
Maybe it would be worth considering alternative storage means, i.e. something that MySQL or RDBMS altogether (for large setups only). Just like Redis for the tracker is optional and meant for large setups. That would mean a huge work on the codebase I can imagine, but if we can (painfully) get a 50% increase on the max volumetry with MySQL will that be enough? Do we need to scale much bigger, like ×10? |
This issue here is not really about scaling further but rather investigate existing issues at current scale (and these issues will get worse / more frequent as we grow and as time goes by). Alternative storage means are discussed in #1999 with focus on mysql engines for now because implementing any other solution (such as a nosql DB) would take us 1+ year of development. Edit: maybe some of these challenges above cannot be solved with Mysql alone and then we can re-assess... but hopefully we can find some smart solutions to some/most of these :-) |
very interesting blog post Avoiding MySQL ALTER table downtime |
A lot of progress has been made (i've edited the issue to cross out issues that are now done). We are continuing to work on performance and will do this one next: scale the Website Manager when there are thousands of websites (#3838) |
Hey Matt, et all, not sure if this is the right place to post this, but I was wondering if there are any procedures for removing features or blocks of features from Piwik setup/DB? I am running analytics engine that takes use of Piwik's Event Tracking engine. We are operating on websites with 3M+ uniques and are looking to grow. Since we aren't using all of the features of PW, perhaps there's a way to "lighten" the whole thing? Like a race car :) |
hi @dmitrisgit, the official way is to disable some plugins from Piwik > Administration > Plugins, this will speed up the Tracker, Archiving, and possibly the UI as well. |
Will now close this issue as we did a lot of work over the last two years and have solved most obvious issues. Piwik 3 will go even further with BIGINT fields to let users track by default more than 4 billion actions & visits. We'll discuss further performance issues/ suggestions in separate issues. Check the tag |
The goal of this issue is to keep track of all the ongoing challenges that come with running Piwik on large traffic websites. These issues may affect Piwik servers with more than 50M actions/pageviews per month.
INT
toBIGINT
for Primary keys to avoid issues whenlog_link_visit_action
table hits 4 billion records (4,294,967,295
) Integer overflow: how to track more than 2 billion actions with PiwiK? #3288Custom date range reports are slow: how to make them faster? Custom date range reports are slow: how to make them archive faster? #4768and Monthly archiving should use the smaller amount of weeks and days inside the month #3611Custom date ranges loaded by default are not pre-processed and timeout Pre-process custom date ranges when users have selected them as their default date range #6672Sub-table implementation becomes slow when thousands of leaves in the tree How to make hierarchical tables scale? (flatten, search, sub tables) #6763and Store blob archives more efficient #7375Make it flat times out when large amount of data "Make it flat" actions/pages report eats server resources when there's a large amount of data #5098High computation load after adding new segments to pre-process Computation load after adding new segments on long existing Piwik instance #6638and New feature for Segments in Segment editor: "Process historical reports from ..." #7483Live.getCounters
times out on very large instance Live.getCounters times out on very large instance #6758Show paging in the screen 'Manage websites' Show paging in the screen 'Manage websites' to easily manage thousands of websites #3838Make archiving faster when thousands of websites with low or no traffic Make archiving faster when thousands of websites with low or no traffic #5922All websites dashboard rendering can timeout or make browser unresponsive All websites dashboard - improve performance when thousands of websites #6809See also ideas to research #1999 and continuous performance integration #2000
The text was updated successfully, but these errors were encountered: