Matt, I am testing to use this in a production environment- a beta version simply wont do for this purpose, it must be a stable, tested build. my timeout is fine and the cron archiving completes within 3 or 4 hours without any errors. It just seems piwik doesn't like to track so many segments and it seems as time goes on it gets worse and worse- more days from more segments just not getting reports created. I can manually query data in the database when I log in, but API calls are triggering rearchiving even when I have browser archiving triggering set to disabled.
browser_archiving_disabled_enforce = 1
enable_browser_archiving_triggering = 0
It seems both of these are being ignored. This wouldn't be nearly so bad if it tried to pull up data and just told me it didn't have any- but it throttles the server costing precious cycles just to take 2 or so hours to pull up a segment that has about 100 hits or so.
browser_archiving_disabled_enforce = 1
enable_browser_archiving_triggering = 0
It seems both of these are being ignored. This wouldn't be nearly so bad if it tried to pull up data and just told me it didn't have any- but it throttles the server costing precious cycles just to take 2 or so hours to pull up a segment that has about 100 hits or so.