Performance during archiving process

Hi,

We have about 3,000 websites tracked on our server and the archiving process makes the server pretty unresponsive. My primary issue with this is that the user navigates around too fast for the system to record our various custom events during the archiving process.

As you can see in the image below, the archiving lasts about an hour, and tracking suffers during that (growing) time period.

  1. Is there a way to have the archiving processed on a server other than the server running Piwik. E.g. could we somehow ship or replicate the content to another server for processing?

  2. Is there a way to make this easier on the system so that analytics are tracked quickly, even if that causes the archiving process to run longer?

Thanks!

Hi, See: How to configure Piwik for speed - Analytics Platform - Matomo

and I would recommend to use this plugin: http://plugins.piwik.org/QueuedTracking

Thanks for your reply.

Unfortunately, we’re not able to use a BETA plugin. The plugin also doesn’t comment on how to transition from the existing mysql to their redis backend.

Is there no way to off-load the archiving process to a different server?

Thank you!

After reading into the first link, it looks like I can set this up behind a load balancer which appears to allow for a single server to handle the archiving, away from production tracking. Can anyone confirm that this eliminates the load on the tracking & UI Web servers?

http://piwik.org/faq/new-to-piwik/faq_134/#faq_134