<?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 EVA 6100 Read Performance in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/eva-6100-read-performance/m-p/995074#M4149</link>
    <description>I have a customer with two EVA SANs - (1) EVA 6100 w/ two disk groups and (1) EVA 4000 with two disk groups.&lt;BR /&gt;
&lt;BR /&gt;
The EVA 6100 appears to operate sufficiently with write operations, but the read operations are extremely slow when comparing with the 4000 SAN.&lt;BR /&gt;
&lt;BR /&gt;
Pathing is optimized, etc, etc...&lt;BR /&gt;
&lt;BR /&gt;
The FC disk group has a total of 56 disks on the 6100.  I'm lucky to get 2500MB per minute (read) when the controller is running practically idle.&lt;BR /&gt;
&lt;BR /&gt;
From the same host, the EVA 4000 easily operates at 6000+ MB per minute.&lt;BR /&gt;
&lt;BR /&gt;
LUN size and vDisk type are configured using vRAID 5.&lt;BR /&gt;
&lt;BR /&gt;
vRAID 1 offers little improvement.&lt;BR /&gt;
&lt;BR /&gt;
Assistance would be greatly appreciated!</description>
    <pubDate>Sun, 31 Aug 2008 02:16:28 GMT</pubDate>
    <dc:creator>Paul .</dc:creator>
    <dc:date>2008-08-31T02:16:28Z</dc:date>
    <item>
      <title>EVA 6100 Read Performance</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-6100-read-performance/m-p/995074#M4149</link>
      <description>I have a customer with two EVA SANs - (1) EVA 6100 w/ two disk groups and (1) EVA 4000 with two disk groups.&lt;BR /&gt;
&lt;BR /&gt;
The EVA 6100 appears to operate sufficiently with write operations, but the read operations are extremely slow when comparing with the 4000 SAN.&lt;BR /&gt;
&lt;BR /&gt;
Pathing is optimized, etc, etc...&lt;BR /&gt;
&lt;BR /&gt;
The FC disk group has a total of 56 disks on the 6100.  I'm lucky to get 2500MB per minute (read) when the controller is running practically idle.&lt;BR /&gt;
&lt;BR /&gt;
From the same host, the EVA 4000 easily operates at 6000+ MB per minute.&lt;BR /&gt;
&lt;BR /&gt;
LUN size and vDisk type are configured using vRAID 5.&lt;BR /&gt;
&lt;BR /&gt;
vRAID 1 offers little improvement.&lt;BR /&gt;
&lt;BR /&gt;
Assistance would be greatly appreciated!</description>
      <pubDate>Sun, 31 Aug 2008 02:16:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-6100-read-performance/m-p/995074#M4149</guid>
      <dc:creator>Paul .</dc:creator>
      <dc:date>2008-08-31T02:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 6100 Read Performance</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-6100-read-performance/m-p/995075#M4150</link>
      <description>Let me guess ... the slow system is runing XCS V6.110?&lt;BR /&gt;&lt;BR /&gt;Log a call with HP and request a small analysis with EVAperf - I bet the system is hit by the prefetch bug. The fix is to upgrade to XCS V6.200.</description>
      <pubDate>Sun, 31 Aug 2008 16:17:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-6100-read-performance/m-p/995075#M4150</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-08-31T16:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 6100 Read Performance</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-6100-read-performance/m-p/995076#M4151</link>
      <description>Thanks for the heads up - I'll open the call asap.&lt;BR /&gt;&lt;BR /&gt;What happens if my customer can't upgrade to CommandView 8.x?&lt;BR /&gt;&lt;BR /&gt;6.2 requires 8.x and 6110 is the minimum version supported by the 6100 SAN!</description>
      <pubDate>Mon, 01 Sep 2008 16:07:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-6100-read-performance/m-p/995076#M4151</guid>
      <dc:creator>Paul .</dc:creator>
      <dc:date>2008-09-01T16:07:25Z</dc:date>
    </item>
  </channel>
</rss>

