Last Updated on July 22, 2019 EDT by Jordan
A customer of mine was seeing a 15 second load time on their WordPress site when clicking on “Comments”.
I installed Query Monitor and saw that the Akismet plugin was running the following SQL command on each comment.
SELECT COUNT(*) FROM wp_comments WHERE user_id = 1820 AND comment_approved = 1;
This query was to show how many comments the user had previously had approved. The query was taking 0.5 seconds per comment listed when you visit the “Comments” page. The page was taking around 15 seconds to load at times. Now if you had this page set to load 100 comments per page, then you’re looking at 60 seconds.
I decided to run an explain on the query to figure out what was going on.
explain SELECT COUNT(*) FROM wp_comments WHERE user_id = 778 AND comment_approved = 1;
Which resulted in the following. (Sorry for the screenshot, copy/pasting and reformatting was not something I wanted to do. Also this references the wp_bspr_comments. This is due to the database having a wp_bspr for it’s table prefix.
As you can see, the query is having to go through 19866 rows within the wp_comments table which is the total amount in the table. Since they’re using count(*) all rows are scanned.
So I decided to add an index for the user_id and comment_approved columns.
create index wp_comments_askismet ON wp_comments (user_id,comment_approved);
No when running an explain, there are only 9 rows scanned.
Load times were reduced dramatically. However, this can all be mitigated if you simply turn of the Akismet feature.
