CAUTION – purging log can stall you server

The redirection worked quite well for a while. But the log table ran full over time, because I nearly forgot about this plugin while working on other construction sites. When I recognized the full log and clicked the clean up button of “404 to 301”, the whole server went down immediately!

I had to call web hoster to reboot the server. They told me this script made WordPress open too many mySQL connections, that way used up all RAM, and caused heavy load on HDDs.

Bad architecture I guess. First, it shouldn’t run endless logging, but terminate itself after a default time. And second, it should clean up the mess in small steps.

I must admit that I can’t tell, if this issue is legacy and if there’s a new version handling things more gracious. But from what I’ve seen on the screenshots, there don’t seem to have been many essential improvements over the last years.