By mediafrenzy on

Hi, I've been looking at how to reduce the size of my drupal database, and quickly found that my accesslog was 125mb of a total of 180mb.

I reduced the log time from 16weeks to 1 week, to see how dramatically it reduced the accesslog table size, but a couple of days later it is still huge, with phpmyadmin saying there is 120mb of "overhead". The number of entries seems to be waaay down, but the overall size is still large due to the overhead.

Can anyone explain to me what that "overhead" is, and how I should resolve this? I'm not confident with mysql or even phpmyadmin, so I just cautiously use phpmyadmin to carry out simple tasks that I've read instructions for.

Am I needing to "optimize" the accesslog table to deal with this overhead?

Thanks

⋅ Categories: Drupal 4.7.x

Comments

armanschwarz’s picture

armanschwarz commented

I came across this while looking for information about accesslog. For anyone in need of an answer (I sure hope the original poster isn't still looking for it!) to this; As mediafrenzy mentioned you can reduce the size of accesslog by decreasing the log time. Entries older than the maximum time will be deleted. This will create overhead in the SQL tables. You can think of this as space that needs to be defragmented to be liberated and made available as free space. For the more mysql savvy of you, just run an OPTIMIZE query on the table to remove the overhead. There is a great module called DB Maintenance which will take care of optimizing tables for you.