Hello-
Who out there is using SQL logging in a high-volume site? We're
handling anywhere from 4-6 million messages per day. We chug along
with an average of about 50-60 log lines per second (we do a log entry
per-user, so one message sent to 5 users will have 5 log entries).
Looking at the logs from the last few weeks, we've seen peaks at over
3500 log lines/second.
We use syslog-ng and a couple of central servers to store all of this.
We run a nightly script that parses the log, creates import files and
does a "load data infile". We have a separate database for each
domain, and a separate table for each month (and are thinking of
switching to daily tables). If we keep up our current growth rate,
we'll double every 3-5 months.
Has anyone used the new SQL logging at high volumes? What's your
experience been? We'd have to modify things a bit, since I don't want
all that data going into single table...any suggestions?
Thanks-
Ed
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
