<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: VPSLink - Unresponsive Support for 17+ Hours</title>
	<atom:link href="http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading/feed" rel="self" type="application/rss+xml" />
	<link>http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading</link>
	<description>Time waits for no man.</description>
	<pubDate>Fri, 29 Aug 2008 02:44:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Shanti A. Braford</title>
		<link>http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-141741</link>
		<dc:creator>Shanti A. Braford</dc:creator>
		<pubDate>Thu, 07 Feb 2008 00:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-141741</guid>
		<description>David,

I gotcha.  So the only way to tell if something is up is by diff'ing the current load against historical averages?

In this particular case, the server was basically unusable, so I knew something was up.  "top" load usually hovered around 1 historically but had jumped to 15.

Was basically looking for a way to "prove" that the server was acting foo bar.

i.e. that it wasn't any of my scripts that started acting rogue.</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>I gotcha.  So the only way to tell if something is up is by diff&#8217;ing the current load against historical averages?</p>
<p>In this particular case, the server was basically unusable, so I knew something was up.  &#8220;top&#8221; load usually hovered around 1 historically but had jumped to 15.</p>
<p>Was basically looking for a way to &#8220;prove&#8221; that the server was acting foo bar.</p>
<p>i.e. that it wasn&#8217;t any of my scripts that started acting rogue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rasch</title>
		<link>http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-141470</link>
		<dc:creator>David Rasch</dc:creator>
		<pubDate>Wed, 06 Feb 2008 12:03:18 +0000</pubDate>
		<guid isPermaLink="false">http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-141470</guid>
		<description>In order to tell if the CPU is overutilized, you'll need to have some control against which to measure it either:
1. do some benchmarking
2. monitor some simple benchmark over time

One thing you could do is monitor and trend the page-load time for pages on your site over time.  This would allow you to see when there were instances of your relatively low utilization, but relatively poor performance.  

The real problem with Load is that on servers like the Web servers I described and Mail servers is that when lots of processes run to handle individual requests, this can drive the load up under semi-normal operations.  One of the primary things you should see are relatively slow changes in load.  Load shouldn't change from 1 to 15 over 10 minutes unless your traffic has also spiked substantially (not too likely unless you discover some event, like a blog post or a new link, and that should show up in your analytics).</description>
		<content:encoded><![CDATA[<p>In order to tell if the CPU is overutilized, you&#8217;ll need to have some control against which to measure it either:<br />
1. do some benchmarking<br />
2. monitor some simple benchmark over time</p>
<p>One thing you could do is monitor and trend the page-load time for pages on your site over time.  This would allow you to see when there were instances of your relatively low utilization, but relatively poor performance.  </p>
<p>The real problem with Load is that on servers like the Web servers I described and Mail servers is that when lots of processes run to handle individual requests, this can drive the load up under semi-normal operations.  One of the primary things you should see are relatively slow changes in load.  Load shouldn&#8217;t change from 1 to 15 over 10 minutes unless your traffic has also spiked substantially (not too likely unless you discover some event, like a blog post or a new link, and that should show up in your analytics).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shanti A. Braford</title>
		<link>http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-140617</link>
		<dc:creator>Shanti A. Braford</dc:creator>
		<pubDate>Tue, 05 Feb 2008 03:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-140617</guid>
		<description>David - I'm actually really curious to learn more about this.

How do I tell then if the CPU really is overutilized?</description>
		<content:encoded><![CDATA[<p>David - I&#8217;m actually really curious to learn more about this.</p>
<p>How do I tell then if the CPU really is overutilized?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rasch</title>
		<link>http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-140606</link>
		<dc:creator>David Rasch</dc:creator>
		<pubDate>Tue, 05 Feb 2008 02:17:25 +0000</pubDate>
		<guid isPermaLink="false">http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-140606</guid>
		<description>Load of 15 just means 15 processes are waiting for the CPU.  This could be a symptom of a completely healthy machine.  Our webservers hover around 15 during a normal operating day (down from 25-30 before we got APC up and running).  That's not to say things aren't going wonky on your server, but Load isn't going to be the best metric for identifying this :)

-David</description>
		<content:encoded><![CDATA[<p>Load of 15 just means 15 processes are waiting for the CPU.  This could be a symptom of a completely healthy machine.  Our webservers hover around 15 during a normal operating day (down from 25-30 before we got APC up and running).  That&#8217;s not to say things aren&#8217;t going wonky on your server, but Load isn&#8217;t going to be the best metric for identifying this <img src='http://sablog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>-David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-133895</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Sun, 27 Jan 2008 06:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://sablog.com/archives/2008/01/26/vpslink-be-careful-when-upgrading#comment-133895</guid>
		<description>Dude, funny you should post about this today...I'm just in the process of wrangling a new VPS myself. I've had a dedicated box for the last couple of years but can't justify the cost anymore so am migrating to a VPS and finding the whole thing pretty painful :(</description>
		<content:encoded><![CDATA[<p>Dude, funny you should post about this today&#8230;I&#8217;m just in the process of wrangling a new VPS myself. I&#8217;ve had a dedicated box for the last couple of years but can&#8217;t justify the cost anymore so am migrating to a VPS and finding the whole thing pretty painful <img src='http://sablog.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
