I'm planning on implementing a new statistics system on my websites, but am a bit worried about the volume of data it will produce.

The database has risen to 5MB in testing and I am expecting it to grow by about 20-25MB per month. Because of this, am I going to have problems running queries on it from PHP?

On my statistics reporting page I make about 5/6 queries at a time on the full database. Am I going to run into problems with this causing excess server usage, or is this sort of database 'small' for MySQL (according to MySQL.com it works fine with 5,000,000,000 rows).

Thanks

Hey there,

I have found that MySQL can perform exceptionally in the higher sizes as long as your server has got the backing power. At what frequency is your site being used?

Also keep in mind, that if the statistics side is just for you, you will not have to worry about split second responses.

Either way, you should be okay!

-Ry

You can outsource the traffic stats button google analytics is the best option to go for

Each page I load makes several hits to my DB too.

Opening a persistant connection aids in this so that you only open 1 connection throw lots of sql at it thern close the connection. This is by far much easier than dealing with open act close DB hits.

If your rows do start to get out of hand you could always cluster your DB into say 3 or 4 DB's load balanced to aid in your gathering.

http://www.howtoforge.com/loadbalanc...cluster_debian givces an idea of how to do that.

Ibbo