Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter dezh

    (@dezh)

    What I want to say is that I wish to log all types of 404s, but I want the way how 404s are logged and stored in wordpress db to get improved.

    Currently, in order to log 404 error, 404 module will retrieve the content of “seo_ultimate_module_404s” option, which is serialized list of all 404 hits, then it will unserialize it, add a new hit to that list, reserialize the list and it will put serialized list back to “seo_ultimate_module_404s” option in wordpress DB.

    In my case, the size of serialized array of 100 404s is ~400kb. When our site got scanned and got tons of 404 errors, our mysql servers almost crashed, because the memory was quickly taken away by ~400kb queries in binary log for replication.

    It would be much nicer for servers to have a log of 1000 4kb queries instead of 1000 400kb queries.

    Thread Starter dezh

    (@dezh)

    bump

Viewing 2 replies - 1 through 2 (of 2 total)