domain_traffic table growing huge

[ispcomm]

File logging by default is OK for me. That can always be changed with a proper "parts" config for apache for more specific configurations (like multi-server as you mentioned).

I like the idea of gplhost because it suits me better (specially when you have a geo-distributed infrastructure), but I agree that for a single server file logging is better.

I woudn't use vlogger then but simple plain combined-compatible file with the %V (or was it %v) directive that prints out the "vhost" in the logs. A nightly (perl) script can easily split it in 200-300 different files and perhaps update the databases.

When daily rotation becomes a problem, a hourly rotation can be implemented.

You loose the "real-time" logs for the customers: Logs will be available the next day or the next hour, but this can be accepted for a shared hosting account. If a customer needs real-time logs they can be pushed to a vps.

ispcomm.