{"id":954,"date":"2018-05-08T19:06:16","date_gmt":"2018-05-08T23:06:16","guid":{"rendered":"https:\/\/www.devolve.net\/blog\/?p=954"},"modified":"2018-07-13T10:59:52","modified_gmt":"2018-07-13T14:59:52","slug":"finding-which-wordpress-requests-are-hardest-on-the-database","status":"publish","type":"post","link":"https:\/\/www.devolve.local\/finding-which-wordpress-requests-are-hardest-on-the-database\/","title":{"rendered":"Finding which WordPress requests are hardest on the database"},"content":{"rendered":"
Everyone says WordPress can handle north of a 100,000 or a million posts, no problem!<\/p>\n
BS<\/strong>. Okay, if you have a dedicated database system with enough RAM to hold the entire dataset, then A)<\/strong> that’s cheating, since RDBMSs were created to handle the case where one doesn’t have the requisite memory<\/em>; and B)<\/strong> I don’t have that luxury right now. I routinely run into lots of performance issues despite a well-tuned LAMP system.<\/p>\n
\n<\/p>\nmysql> select count(1) from wp_posts;\r\n+----------+\r\n| count(1) |\r\n+----------+\r\n| 1153099 |\r\n+----------+\r\n1 row in set (0.72 sec)\r\nmysql> select count(1) from wp_terms;\r\n+----------+\r\n| count(1) |\r\n+----------+\r\n| 65797 |\r\n+----------+\r\n1 row in set (0.04 sec)\r\n<\/pre>\n