Bug after 10 000 visitor by day

Hello, piwik see bug after 10 000 visitor by day, few time show 10 200 visitor, other time 0 visitor (for yesterday), on all site and dashboard.
Some body can help my?
And piwik is very slow on large site. mainly in today statistics.

Piwik can use other than mysql? (postgresql?)

Thanks for yourhelp.

watch for perf improvements in 1.3.

official postgresql support is on my todo list but on the backburner for the moment.

check out the new RC which improves a bit performance: 301 Moved Permanently

And about statistic broken?
Some time 0 visits, F5, 11 000 visits…, rand ( 0 or real number)…

You must setup auto archiving: How to Set up Auto-Archiving of Your Reports - Analytics Platform - Matomo

This will fix the issue “sometimes zero, sometimes not zero”

For previous reports if you have some zero, please delete your archive table archive_*

I have already setup auto archiving because I know since the start the large audience.
All previous data seam be ok, the data seam be ok because some time is right and other time is wrong (then data is ok, but display/interface show wrong data).

The screenshot of my bug…

Any idea?

i have this problem too :frowning:

have you uploaded the latest RC? 301 Moved Permanently

yes, it’s change nothing, update since 2 days.


Have you set General settings > Timeout to 3600 s for example, then setup crontab?

Is daily stats working ? Only month stats are not working?

Crontab in place, no timeout (infinity execution time).
The bug put to 0 the stat of day, and few day after the stat is ok, see the new screenshot of exactly the same site.

you have stats on this screenshot so what is the problem?

also what does mean "no timeout (infinity execution time). " please explain your problem better…

The hole is present or not. It’s my probleme.


a little off topic, what did you do to get that increase in traffic???

nice i want one


The webmaster (I’m the developper and systeme administrator), have buy trafic.

check php’s memory_limit. that’s a more common constraint than max_execution_time.

have you tried dropping your archive tables to allow the script to regenerate them?

Yes, I have try all.