Hey Max!
Great to hear from you, thank you! So just to clarify, are you seeing what was causing the full-table-scan of the logins table on each load of wp-login.php?
And is there a way to remove the scanning of that table for the login process?
It took a while to figure out that's what was causing it - but apparently there are some very common wordpress attacks in the wild now, doing lots and lots of submit to wp-login.php to try and break into a site. i.e. dictionary attacks.
That's not really a problem for us, BUT our login log table has over 100k entries and keeps growing - we need to keep that data for a long period (read: indefinitely)... we don't purge it.
So I just need to ensure that the login process does not scan that table. :-)
Thanks!!
↧
Dan & Jennifer on "[Plugin: Simple Login Log] Performance issue: SELECT * FROM wp_simple_login_log on each hit of wp-login.php"
↧