We are currently looking at Piwik as a possibility for replacing the current logfile/webalizer solution that we use to provide stats for around 10,000 websites, that generate combined pageviews of over 1 million a day.
Has Piwik been tested with this volume of sites/traffic and what sort of hardware could we expect to need to support growth up to at least double those figures?
I would suggest that you slowly build up traffic (starting with 100k eg.) and maybe try to do the change in #1227 (and submit the patch) if you can. We are very interested by your experience. Also, making Piwik work on such scale is definitely part of our Piwik 1.0 roadmap, but we haven’t yet started doing stress testing ourselves at this scale.
I committed the fix to the ticket 1227 which should help a lot with your setup, because you have thousands of websites. Let us know how it’s working for you.
The first bottleneck always was the memory used during the archiving process (PHP memory). The patch to archive.sh should help a lot with this. After, depending on traffic, other bottlenecks might appear, such as Tracking data get slower, etc. We haven’t made tests so I can’t say for sure, the best way would be to test it. Let us know how it’s working and when problems appear, we’ll definitely want to help fixing them!
Its very help full for me because few days i am learning about the websites and this site have more information. i should follow your all tips if you have not any problem than please send me link where i get good templates.