Hello out there...
Tom Wiebe Lists <[email protected]>
| Newsgroups | gmane.comp.apache.mod-log-sql |
|---|---|
| Message-ID | <[email protected]> |
Hi there, Not sure if this list is still up or not, I've only received 1 message in the last 2 months. mod_log_sql has been purring along just tickety-boo though, so it hasn't been much of an issue til now. My problem now is that I'm swimming in data, my servers have generated nearly 2 gigs worth of mysql tables in the last 5 months and now I'm starting to wonder how to go about maintaining it over the long term. My logging machine is just a lowly 1 gig Celeron (that hardly breaks a sweat keeping up with mod_log_sql), so while it's going great right now, I'm sure it will start to crawl a bit as things grow. Using myisampack and merge tables looks like a valid route to go, e.g. given a host foo.com I would once a month dump the records in access_foo_com into access_foo_com_year_month (or something to that effect), run myisampack on it and then, if I understand the limited documetation for mysql merge tables, create a merge table that contains access_foo_com, access_foo_com_2003_03, access_foo_com_2003_04 etc and query that to find out my results on an ongoing basis. Or have I understood wrong? What is everybody else doing? from the sound of things this module is being used in some fairly large ISP's etc. Surely someone smarter than I has come up with a solution for this. TIA, Tom Wiebe __________________________________________________________________ Reminder: to unsubscribe, send email to <[email protected]> with the words "unsubscribe mod_log_sql" in the body (w/o quotes). The module homepage is http://www.grubbybaby.com/mod_log_sql/