 




<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Meeting IT&#8217;s server SLA obligations</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/meeting-its-server-sla-obligations/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/meeting-its-server-sla-obligations/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 15:11:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: sunsetrider</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/meeting-its-server-sla-obligations/#comment-82294</link>
		<dc:creator>sunsetrider</dc:creator>
		<pubDate>Tue, 12 Oct 2010 00:20:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-82294</guid>
		<description><![CDATA[There&#039;s a saying in business - if you can&#039;t measure it, you can&#039;t manage it.    

The secret is to measure meaningful activities.  A long, long time ago, we had an arrangement with a computer manufacturer that guaranteed a very high up-time percentage which was maintained.  Unfortunately, our resonse time was very lousy.  We should have measured response time (how quickly the network/computer could reply to customers&#039; queries). When we changed the metrics, we were able to identify short-comings, identify solutions and apply them.

The availability can be 99.999999%, but if response is slow (such as 4+ minutes to boot-up network computers) it is not acceptable. Up-time is important, but response time should also be included in the mix. 

Define useful metrics, not just something that can easily be displayed, and really doesn&#039;t show much.]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s a saying in business &#8211; if you can&#8217;t measure it, you can&#8217;t manage it.    </p>
<p>The secret is to measure meaningful activities.  A long, long time ago, we had an arrangement with a computer manufacturer that guaranteed a very high up-time percentage which was maintained.  Unfortunately, our resonse time was very lousy.  We should have measured response time (how quickly the network/computer could reply to customers&#8217; queries). When we changed the metrics, we were able to identify short-comings, identify solutions and apply them.</p>
<p>The availability can be 99.999999%, but if response is slow (such as 4+ minutes to boot-up network computers) it is not acceptable. Up-time is important, but response time should also be included in the mix. </p>
<p>Define useful metrics, not just something that can easily be displayed, and really doesn&#8217;t show much.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.030 seconds using memcached
Object Caching 267/273 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-23 17:07:28 -->