CRP can overload the DB server on a large site, even with the latest workarounds
Replies: 0
Months ago, I noticed my very large site (over 370k posts) slowing down to a crawl, and then becoming unresponsive until the DB was restarted. I found #sql-temptable-*.MAD and .MAI files collecting in the tmp directory – it was a backlog of queries that the server couldn’t keep up with, as robots and users hit the site. Running mysql -e “show full processlist” | grep -v “Sending data” revealed this, and further diagnosis showed CRP was the WP plugin doing these expensive queries.
Disabling CRP as soon as the #sql-temptable files begin appearing, allows the DB to catch up, and doesn’t destroy performance. This is a very crude way of protecting the DB server from the CRP plugin – I would rather see the plugin monitor itself, and refuse to run the query if SHOW PROCESSLIST tells it there is a backlog of queries forming.
CRP is the best plugin of its kind in the “Related Posts” category. The query it runs seems essential to its success story – and so would a proactive check (as suggested) to assure it doesn’t take the DB server down in high-load periods. I’m sure any admin would rather see the plugin briefly/automatically stop listing Related Posts, and play it safe.
Thanks!
- This topic was modified 4 minutes ago by .
مشاهده پاسخ های این مطلب
———————————————
این مطلب از سایت انجمن وردپرس گردآوری شده است و کلیه حقوق مطلق به انجمن وردپرس می باشد در صورت مغایرت و یا بروز مشکل اطلاع دهید تا حذف گردد
منبع: انجمن وردپرس