<?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: ML350 G5 Array 200i SLOW write speeds in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424198#M90901</link>
    <description>Hi Dave, &lt;BR /&gt;&lt;BR /&gt;Do you know if the E200i has the BBWC? bascially... does it have a battery attached? if not then your cache on the controller is only being used for reads.</description>
    <pubDate>Thu, 21 May 2009 16:33:04 GMT</pubDate>
    <dc:creator>SMR</dc:creator>
    <dc:date>2009-05-21T16:33:04Z</dc:date>
    <item>
      <title>ML350 G5 Array 200i SLOW write speeds</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424197#M90900</link>
      <description>When copying files the performance is very slow. There are three SATA drives in a RAID 5 array.  OS is Windows Server 2003  A 60GB file transfer took over three hours from a 3Gbps eSATA drive.  Other servers and desktops with a single SATA internal drive connected to the same external eSATA drive take far less time.  This is having a significant impact on employees.  Suggestions?</description>
      <pubDate>Thu, 21 May 2009 10:57:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424197#M90900</guid>
      <dc:creator>Dave McAdams</dc:creator>
      <dc:date>2009-05-21T10:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G5 Array 200i SLOW write speeds</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424198#M90901</link>
      <description>Hi Dave, &lt;BR /&gt;&lt;BR /&gt;Do you know if the E200i has the BBWC? bascially... does it have a battery attached? if not then your cache on the controller is only being used for reads.</description>
      <pubDate>Thu, 21 May 2009 16:33:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424198#M90901</guid>
      <dc:creator>SMR</dc:creator>
      <dc:date>2009-05-21T16:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G5 Array 200i SLOW write speeds</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424199#M90902</link>
      <description>It is the model with a 128 BBWC.  I should have added that originally.</description>
      <pubDate>Thu, 21 May 2009 17:20:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424199#M90902</guid>
      <dc:creator>Dave McAdams</dc:creator>
      <dc:date>2009-05-21T17:20:41Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G5 Array 200i SLOW write speeds</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424200#M90903</link>
      <description>So if you have a fully charged and functional battery then you might want to tweak your cache ratio, from my experience some environments benefit from 50/50 others from 75/25. Give it a try and post the result. An ADU report would be useful to check for errors.</description>
      <pubDate>Thu, 21 May 2009 23:51:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424200#M90903</guid>
      <dc:creator>SMR</dc:creator>
      <dc:date>2009-05-21T23:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G5 Array 200i SLOW write speeds</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424201#M90904</link>
      <description>Update firmware. Update drivers. Use HP utility (don't remember name of it) to enable INTERNAL drives cache. It disabled by default, unlike all other PC's. No other ways to make this thing fast.</description>
      <pubDate>Fri, 22 May 2009 09:15:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/4424201#M90904</guid>
      <dc:creator>PussPower</dc:creator>
      <dc:date>2009-05-22T09:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G5 Array 200i SLOW write speeds</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/6738044#M148268</link>
      <description>&lt;P&gt;For me it worked to enable disk INTERNAL cache via HP Smart Storage administrator.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The speeds (although initializing parity on the RAID5 volume) went from 0-30 (sometimes it completely stopped) to steady 50-100MB.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Perhaps it getting even better when parity is complete.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2015 13:36:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/6738044#M148268</guid>
      <dc:creator>iceman38</dc:creator>
      <dc:date>2015-04-28T13:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G5 Array 200i SLOW write speeds</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/6739884#M148349</link>
      <description>&lt;P&gt;E200i is just very awful controller, performance issues are well known. You can tweak settings as suggested or replace controller with better one.&lt;/P&gt;</description>
      <pubDate>Fri, 01 May 2015 04:32:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g5-array-200i-slow-write-speeds/m-p/6739884#M148349</guid>
      <dc:creator>MM_Z</dc:creator>
      <dc:date>2015-05-01T04:32:41Z</dc:date>
    </item>
  </channel>
</rss>

