Yeah, like I said, I think if you optimize that one query somehow, either with indexes, or something like keeping a separate table for known spammers so it's quicker lookup/update than using the main log table then it won't be a problem. I don't mind the storage space for the large logs. Soon as we jump to the new server, there should be disk space to spare. (It's a raid5 setup with 960GB of usable space.) Lemme know if there anything I can do to help you optimize or figure things out. That slow-query log function that mysql has is quite handy, I'd never used it before.