<?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: IBM FC #4319 disk drives</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/ibm-fc-4319-disk-drives/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/ibm-fc-4319-disk-drives/</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 20:45:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: iseriesguy2</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/ibm-fc-4319-disk-drives/#comment-39955</link>
		<dc:creator>iseriesguy2</dc:creator>
		<pubDate>Thu, 19 Jan 2006 12:03:01 +0000</pubDate>
		<guid isPermaLink="false">#comment-39955</guid>
		<description><![CDATA[My reference has been the system report from performance tools to determine how busy your current drives are. The operations  per second on the drives should not exceed 30 on average per drive. It also depends on the IOP you have and how many drives you have on the IOP and the application that&#039;s running on the system. The drive information can also be found on on the system report. If ops per second exceed 30 or are close, adding higher capacity drives on the same IOP will only make matters worse. If this is the case, I would suggest investing $900.00 for a higher cache IOP for the drives and that will alleviate some of the performance botleneck.]]></description>
		<content:encoded><![CDATA[<p>My reference has been the system report from performance tools to determine how busy your current drives are. The operations  per second on the drives should not exceed 30 on average per drive. It also depends on the IOP you have and how many drives you have on the IOP and the application that&#8217;s running on the system. The drive information can also be found on on the system report. If ops per second exceed 30 or are close, adding higher capacity drives on the same IOP will only make matters worse. If this is the case, I would suggest investing $900.00 for a higher cache IOP for the drives and that will alleviate some of the performance botleneck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrdave60</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/ibm-fc-4319-disk-drives/#comment-39956</link>
		<dc:creator>mrdave60</dc:creator>
		<pubDate>Thu, 19 Jan 2006 07:39:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-39956</guid>
		<description><![CDATA[Seek times and MTBF numbers for these two types of drives are about the same.  I have over 100 of the 35gb drives and average about one failure every 6 or 8 months.

There is a command you can use that will give you an idea if performance will be a problem.  It is WRKDSKSTS.  There is a column titled % busy.  As a rule, this number should not exceed about 30%.  I would suggest taking a couple of 15 minute samples at different time of the day to see what your current number is.  If you plan on doubling the capacity of the drives you want this number to be less than 15 to 20 percent with the 17bg drives.

Hope this helps.]]></description>
		<content:encoded><![CDATA[<p>Seek times and MTBF numbers for these two types of drives are about the same.  I have over 100 of the 35gb drives and average about one failure every 6 or 8 months.</p>
<p>There is a command you can use that will give you an idea if performance will be a problem.  It is WRKDSKSTS.  There is a column titled % busy.  As a rule, this number should not exceed about 30%.  I would suggest taking a couple of 15 minute samples at different time of the day to see what your current number is.  If you plan on doubling the capacity of the drives you want this number to be less than 15 to 20 percent with the 17bg drives.</p>
<p>Hope this helps.</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 6/8 queries in 0.013 seconds using memcached
Object Caching 283/284 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-18 21:09:22 -->