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

Disable tracking during archiving #3555

Closed
anonymous-matomo-user opened this issue Nov 17, 2012 · 1 comment
Closed

Disable tracking during archiving #3555

anonymous-matomo-user opened this issue Nov 17, 2012 · 1 comment
Labels
c: Performance For when we could improve the performance / speed of Matomo. duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@anonymous-matomo-user
Copy link

I'd like to request a feature which would temporarily disable tracking during the archiving process (so when table locks on the tracking tables are attained the tracking should be disabled).

Why?

Archiving (when we run the task every hour) takes about 3-5 minutes during which our webpages will seem to never finish loading (everything is there though, the browser is simply waiting for a reply from Piwik). For us this is not acceptable and as such we would prefer Piwik to temporarily disable tracking.

An additional note is that even if tracking is not disabled during the archiving most actions during that period will be lost anyway, because the user will already be on another page. (Or does the script not exit on user abort?)

In my opinion adding this as a setting would increase the usability of Piwik on medium sized websites.


First of all: does Piwik acquire table locks on the following tables during archiving: piwik_log_link_visit_action, piwik_log_visit and/or piwik_log_action? If not you can ignore the following.

Another option might be the following:

It appears the 'piwik_log_link_visit_action' table is the largest and as far as I can tell a (visitor initiated) query will never have to read from this table (because it simply records each time a page is viewed).

So if you were to use two tables: 'piwik_log_link_visit_action_A' and 'piwik_log_link_visit_action_B' you could achieve a table lock on A and write all new actions to B, after which you would acquire a table lock on B and write all new actions to A.

I include this as a second suggestion because this will probably require some major rewrites in the code, but I do think it will allow Piwik to track much larger websites efficiently.

You could of course even expand this concept into having the 'piwik_log_link_visit_action' table spread over different servers.

@robocoder
Copy link
Contributor

duplicate of #3552

@anonymous-matomo-user anonymous-matomo-user added this to the 1.12.x - Piwik 1.12.x 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
Labels
c: Performance For when we could improve the performance / speed of Matomo. duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

2 participants