<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cache on Smart Array 5i plus in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338101#M87126</link>
    <description>thank you all</description>
    <pubDate>Fri, 16 Jan 2009 07:25:41 GMT</pubDate>
    <dc:creator>Anna Cheng</dc:creator>
    <dc:date>2009-01-16T07:25:41Z</dc:date>
    <item>
      <title>Cache on Smart Array 5i plus</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338096#M87121</link>
      <description>&lt;BR /&gt;I am looking into the write performance and have a few questions on the cache. Hope someone may know the answer.&lt;BR /&gt;&lt;BR /&gt;a. for the smart Array 5i Plus controller, and without  BBWC, will there be any cache or memory on the controller?&lt;BR /&gt;&lt;BR /&gt;b. I assume the answer for (a) is no. If so, how can we find out what is the allocation for read/write? will it be 50% for read and 50% for write? can it be changed?&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;</description>
      <pubDate>Thu, 15 Jan 2009 07:10:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338096#M87121</guid>
      <dc:creator>Anna Cheng</dc:creator>
      <dc:date>2009-01-15T07:10:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cache on Smart Array 5i plus</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338097#M87122</link>
      <description>Hi Anna,&lt;BR /&gt;&lt;BR /&gt;   Following are the answers for your queries.&lt;BR /&gt;&lt;BR /&gt;A. smart Array 5i Plus controller has &lt;BR /&gt;64mb onboard memory(apart from the memory that you add on.)&lt;BR /&gt;&lt;BR /&gt;B.To see the performance Read and Write.YOu could use Array configuration utility, Highlight the controller, then Use controller properties or statistics on the right hand side.A new window appears.Which would show you all the details.&lt;BR /&gt;&lt;BR /&gt;Following are Features of Smartarray 5i Plus:&lt;BR /&gt;*********************************************&lt;BR /&gt;Key Products Features&lt;BR /&gt;********************* &lt;BR /&gt;Smart Array 5i Plus &lt;BR /&gt;Increased performance over the Integrated Smart Array Controller and the Smart Array 5i Controller. &lt;BR /&gt;Transportable, hardware-based Wide Ultra3 SCSI RAID controller, with 64MB of memory. &lt;BR /&gt;More robust and easier to use than software-based RAID. &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Try and let us know.</description>
      <pubDate>Thu, 15 Jan 2009 13:50:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338097#M87122</guid>
      <dc:creator>Vulcan Maximus</dc:creator>
      <dc:date>2009-01-15T13:50:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cache on Smart Array 5i plus</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338098#M87123</link>
      <description>Without BBWC, the cache is use for read cache only = 100% used for read cache.&lt;BR /&gt;&lt;BR /&gt;With BBWC the cache is use for read and write cache.&lt;BR /&gt;If i remember correctly default is 50 / 50%&lt;BR /&gt;&lt;BR /&gt;You can see and change that using the ACU&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;/jag</description>
      <pubDate>Thu, 15 Jan 2009 14:46:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338098#M87123</guid>
      <dc:creator>gregersenj</dc:creator>
      <dc:date>2009-01-15T14:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cache on Smart Array 5i plus</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338099#M87124</link>
      <description>thank you both.&lt;BR /&gt;&lt;BR /&gt;gregersenj,&lt;BR /&gt;does it mean that it is the *same* 64MB cache, but when I included BBWC, then the cache will become writable?&lt;BR /&gt;</description>
      <pubDate>Thu, 15 Jan 2009 16:04:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338099#M87124</guid>
      <dc:creator>Anna Cheng</dc:creator>
      <dc:date>2009-01-15T16:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: Cache on Smart Array 5i plus</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338100#M87125</link>
      <description>Correct, at the default of 50%/50% the 64MB would become 32MB read cache and 32MB write cache. The batteries are there in case the server loses power and data has arrived in cache but has not been written to disk yet, then when power is restored to the server the controller will complete the write operation to disk, so no battery = loss of unwritten data.</description>
      <pubDate>Thu, 15 Jan 2009 17:23:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338100#M87125</guid>
      <dc:creator>Greybeard</dc:creator>
      <dc:date>2009-01-15T17:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cache on Smart Array 5i plus</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338101#M87126</link>
      <description>thank you all</description>
      <pubDate>Fri, 16 Jan 2009 07:25:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/cache-on-smart-array-5i-plus/m-p/4338101#M87126</guid>
      <dc:creator>Anna Cheng</dc:creator>
      <dc:date>2009-01-16T07:25:41Z</dc:date>
    </item>
  </channel>
</rss>

