<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<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>Comments on: Wordpress/PHP Help</title>
	<link>http://averyfineline.com/2007/11/01/wordpressphp-help/</link>
	<description>Criticism and commentary on southern gospel music</description>
	<pubDate>Sat, 11 Feb 2012 06:19:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: Web Hosting &#187; Comment on Wordpress/PHP Help by bguy</title>
		<link>http://averyfineline.com/2007/11/01/wordpressphp-help/#comment-196025</link>
		<dc:creator>Web Hosting &#187; Comment on Wordpress/PHP Help by bguy</dc:creator>
		<pubDate>Thu, 15 Nov 2007 06:28:15 +0000</pubDate>
		<guid>http://averyfineline.com/2007/11/01/wordpressphp-help/#comment-196025</guid>
		<description>[...] You can read the rest of this blog post by going to the original source, here [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] You can read the rest of this blog post by going to the original source, here [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bguy</title>
		<link>http://averyfineline.com/2007/11/01/wordpressphp-help/#comment-181124</link>
		<dc:creator>bguy</dc:creator>
		<pubDate>Fri, 02 Nov 2007 15:34:34 +0000</pubDate>
		<guid>http://averyfineline.com/2007/11/01/wordpressphp-help/#comment-181124</guid>
		<description>hi, Christine Kane said you were having some problems... (i'm her we'bguy' - i handle her we'blog')

first off, i can tell you that bad programming can cause excessive CPU usage. this may not be the first thing i would bet is wrong, but it is the first thing that pops in my head.

any kind of dynamic (performed in real time) tasks that PHP does, can potentially get bogged down by an infinite loop or trying to continue a task regardless of failure (like failing to connect to a remote server - it will try a few times) or simply the sheer size of the task (like a database query that inadvertently pulls way too much info).

if the problem really is PHP (WordPress), i would look at plugins first to find a culprit there. plugins are often not fully tested, or they are released with the disclaimer "alpha version" - which at least advertises that it's not fully tested. they may also conflict with each other.

next, i would look specifically at the index.php file and find any code where PHP performs a task that uses looping or remote connection (displaying an image that lives on another server IS a remote connection and is VERY frowned upon because you use up their bandwidth for your gain). if i had my hands on the code, i would do a few things to time each task execution - but i won't discuss that here cause it's too tecky-geeky. even simple HTML calling for a remote image can create the same problems (after all, PHP is HTML when it's sent out to the visitor).

now... aside from PHP/WordPress coding issues... i notice that you refer many times to your ISP in regards to your website. well, your ISP = Internet Service Provider.... they provide you with your "internet service" NOT "web hosting".  it's like thinking of your phone company as your landlord... which is CRAZY... UNLESS your ISP also HAPPENS to provide web hosting services as well (providing a place to store and serve your website).

if we set aside the idea that you ISP has anything to do with this (regardless of whether they are the same entity) and focus on the who you really mean to refer to, you Hosting Provider, we can look at some other possibilities.

there are many levels of web hosting. a "server" is a "label" for: a computer that stores files remotely and allows other computers to make remote connection requests that ask for various files (primarily HTML web page files) and "serves" them to the requesting computers. just like all the other computers, it can be built with different hardware and have different levels of performance.

any particular server (low/high performance) can act as a server for one website, a few websites, a lot of websites, or a WHOLE LOT of websites. when you put mulitple websites on the same server, all those websites must SHARE EVERYTHING about that computer -- especially CPU and RAM. 

"shared hosting" is usually very cheap $5-12 per month or so. invariably, shared hosting servers are MUCH slower -- they are MUCH more prone to resource shortage (ex: CPU and RAM), MUCH more prone to application crashing (MySQL database for example). they often have limitations to try to alleviate this and distribute equally to all of the sites on the server -- which really means your website is served up more slowly ALL OF THE TIME (think of your car, capabale of 100+ MPH limited to 35 MPH on a 2-lane city road).  and to make money, the hosting providers must CRAM as may websites as they can on each server.

i guarantee if your hosting provider is calling you out on CPU usage -- you're on a shared server.  otherwise, the CPU would be yours alone to get as much out of it as you could - you could "floor it" so to speak. 

but because you're on a shared server, your site may simply be generating enough traffic and/or making other requests that exceed your measly slice of the CPU pie. it may not have anything at all to do with bad PHP WordPress code (plugins or not), but a lot more to to do with bad web hosting service (or, at the least, "get what you pay for" web hosting service). in other words, your same site on another server may not have any issues AT ALL -- AND WITHOUT CHANGING A THING -- if it were on a "higher quality hosting level".

if you're using some free service from your ISP (if they so happen to provide that -- and some do, like BellSouth) you are REALLY in trouble.  for obvious reasons, the free stuff is the cheapest and the lowest peformance.

so you have 2 things to look at...
1) find exactly where WordPress is generating content or performing a task that is a HUGE task (it could be behind the scenes)
	i looked at your main page and there is NOTHING on the surface that could even remotely cause it.  also, i don't want to burst your bubble, but you would have to generate a LOT of traffic -- i mean MAJOR traffic -- to exceed the CPU limitations... (unless the CPU limitation was small)
	(i doubt your problem is #1)

2) just what level of web hosting service do you have?
	the answer to this question is verly likely the answer to the problem...</description>
		<content:encoded><![CDATA[<p>hi, Christine Kane said you were having some problems&#8230; (i&#8217;m her we&#8217;bguy&#8217; - i handle her we&#8217;blog&#8217;)</p>
<p>first off, i can tell you that bad programming can cause excessive CPU usage. this may not be the first thing i would bet is wrong, but it is the first thing that pops in my head.</p>
<p>any kind of dynamic (performed in real time) tasks that PHP does, can potentially get bogged down by an infinite loop or trying to continue a task regardless of failure (like failing to connect to a remote server - it will try a few times) or simply the sheer size of the task (like a database query that inadvertently pulls way too much info).</p>
<p>if the problem really is PHP (WordPress), i would look at plugins first to find a culprit there. plugins are often not fully tested, or they are released with the disclaimer &#8220;alpha version&#8221; - which at least advertises that it&#8217;s not fully tested. they may also conflict with each other.</p>
<p>next, i would look specifically at the index.php file and find any code where PHP performs a task that uses looping or remote connection (displaying an image that lives on another server IS a remote connection and is VERY frowned upon because you use up their bandwidth for your gain). if i had my hands on the code, i would do a few things to time each task execution - but i won&#8217;t discuss that here cause it&#8217;s too tecky-geeky. even simple HTML calling for a remote image can create the same problems (after all, PHP is HTML when it&#8217;s sent out to the visitor).</p>
<p>now&#8230; aside from PHP/WordPress coding issues&#8230; i notice that you refer many times to your ISP in regards to your website. well, your ISP = Internet Service Provider&#8230;. they provide you with your &#8220;internet service&#8221; NOT &#8220;web hosting&#8221;.  it&#8217;s like thinking of your phone company as your landlord&#8230; which is CRAZY&#8230; UNLESS your ISP also HAPPENS to provide web hosting services as well (providing a place to store and serve your website).</p>
<p>if we set aside the idea that you ISP has anything to do with this (regardless of whether they are the same entity) and focus on the who you really mean to refer to, you Hosting Provider, we can look at some other possibilities.</p>
<p>there are many levels of web hosting. a &#8220;server&#8221; is a &#8220;label&#8221; for: a computer that stores files remotely and allows other computers to make remote connection requests that ask for various files (primarily HTML web page files) and &#8220;serves&#8221; them to the requesting computers. just like all the other computers, it can be built with different hardware and have different levels of performance.</p>
<p>any particular server (low/high performance) can act as a server for one website, a few websites, a lot of websites, or a WHOLE LOT of websites. when you put mulitple websites on the same server, all those websites must SHARE EVERYTHING about that computer &#8212; especially CPU and RAM. </p>
<p>&#8220;shared hosting&#8221; is usually very cheap $5-12 per month or so. invariably, shared hosting servers are MUCH slower &#8212; they are MUCH more prone to resource shortage (ex: CPU and RAM), MUCH more prone to application crashing (MySQL database for example). they often have limitations to try to alleviate this and distribute equally to all of the sites on the server &#8212; which really means your website is served up more slowly ALL OF THE TIME (think of your car, capabale of 100+ MPH limited to 35 MPH on a 2-lane city road).  and to make money, the hosting providers must CRAM as may websites as they can on each server.</p>
<p>i guarantee if your hosting provider is calling you out on CPU usage &#8212; you&#8217;re on a shared server.  otherwise, the CPU would be yours alone to get as much out of it as you could - you could &#8220;floor it&#8221; so to speak. </p>
<p>but because you&#8217;re on a shared server, your site may simply be generating enough traffic and/or making other requests that exceed your measly slice of the CPU pie. it may not have anything at all to do with bad PHP WordPress code (plugins or not), but a lot more to to do with bad web hosting service (or, at the least, &#8220;get what you pay for&#8221; web hosting service). in other words, your same site on another server may not have any issues AT ALL &#8212; AND WITHOUT CHANGING A THING &#8212; if it were on a &#8220;higher quality hosting level&#8221;.</p>
<p>if you&#8217;re using some free service from your ISP (if they so happen to provide that &#8212; and some do, like BellSouth) you are REALLY in trouble.  for obvious reasons, the free stuff is the cheapest and the lowest peformance.</p>
<p>so you have 2 things to look at&#8230;<br />
1) find exactly where WordPress is generating content or performing a task that is a HUGE task (it could be behind the scenes)<br />
	i looked at your main page and there is NOTHING on the surface that could even remotely cause it.  also, i don&#8217;t want to burst your bubble, but you would have to generate a LOT of traffic &#8212; i mean MAJOR traffic &#8212; to exceed the CPU limitations&#8230; (unless the CPU limitation was small)<br />
	(i doubt your problem is #1)</p>
<p>2) just what level of web hosting service do you have?<br />
	the answer to this question is verly likely the answer to the problem&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

