domain_traffic table growing huge

[kilburn]

I prefer a file-based logging solution for multiple reasons:

1. Logs can be stored with the users data (/var/www/virtual/user), counting on disk quota and easing backups.
2. It gives better performance.
3. No network-related errors (mysql server could be down, you could severly drain bandwidth, raise latency, etc.)
4. Almost everything is logged the same way

I think that your proposal is better for a grid of a couple machines, but not on a single one (wich I guess is the most used configuration of ispcp as of now).

What would you think about file logging and (optional) file-to-sql feeding with aggresive rotation. This way you get the best of both worlds...