<?xml version="1.0" encoding="UTF-8"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>WordPress &#8250; Support Topic: [Plugin: Broken Link Checker] CPU Hog</title>
<link>http://wordpress.org/support/</link>
<description>WordPress &#8250; Support Topic: [Plugin: Broken Link Checker] CPU Hog</description>
<language>en</language>
<pubDate>Tue, 24 Nov 2009 07:21:24 +0000</pubDate>

<item>
<title>ZenKimchi on "[Plugin: Broken Link Checker] CPU Hog"</title>
<link>http://wordpress.org/support/topic/223868#post-919466</link>
<pubDate>Wed, 10 Dec 2008 14:15:56 +0000</pubDate>
<dc:creator>ZenKimchi</dc:creator>
<guid isPermaLink="false">919466@http://wordpress.org/support/</guid>
<description>&#60;p&#62;I was having &#34;500 Server Error&#34; messages for a while and was even kicked off my host this week for excessive CPU usage.  When my host let me back up for 24 hours to fix the problem, I found that the Broken Link Checker plugin was the culprit on all my sites.  Clearing the database tables for the plugin helped temporarily.&#60;/p&#62;
&#60;p&#62;To show what a difference the plugin makes, here's the CPU usage before turning it on:&#60;br /&#62;
34 queries. 1.224 seconds.&#60;/p&#62;
&#60;p&#62;And after turning it on:&#60;br /&#62;
44 queries. 30.251 seconds
&#60;/p&#62;</description>
</item>

</channel>
</rss>
