<?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 EVA4400 performance documentation in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712341#M46805</link>
    <description>&lt;!--!*#--&gt;Could anybody refer me to an HP documentation where I can find information on general IOPS calculations/sizing and respective calculations depending on vRAID 1,5,6?. &lt;BR /&gt;&lt;BR /&gt;I already checked these ones but did not find it &lt;BR /&gt;&lt;A href="http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-0994ENW.pdf" target="_blank"&gt;http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-0994ENW.pdf&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;EVA4400 performance white paper 4AA1-8473ENW&lt;BR /&gt;&lt;BR /&gt;I have seen different ITRC posts suggesting a general estimation of 170-200 IOPS for 15K drives and 120-150 for 10K drives. &lt;BR /&gt;&lt;BR /&gt;I am trying to determine a performance baseline of an EVA and to know whether is overloaded or reaching max performance capacity with the current configuration. &lt;BR /&gt;&lt;BR /&gt;EVA4400 w/ dual controllers (09534000 firmware)&lt;BR /&gt;4GB total cache &lt;BR /&gt;2x Embedded 8GB switches&lt;BR /&gt;24x 450GB 15k &amp;amp; 10x 146GB 15K drives.</description>
    <pubDate>Thu, 11 Nov 2010 21:02:01 GMT</pubDate>
    <dc:creator>Xavi.e.r</dc:creator>
    <dc:date>2010-11-11T21:02:01Z</dc:date>
    <item>
      <title>EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712341#M46805</link>
      <description>&lt;!--!*#--&gt;Could anybody refer me to an HP documentation where I can find information on general IOPS calculations/sizing and respective calculations depending on vRAID 1,5,6?. &lt;BR /&gt;&lt;BR /&gt;I already checked these ones but did not find it &lt;BR /&gt;&lt;A href="http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-0994ENW.pdf" target="_blank"&gt;http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-0994ENW.pdf&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;EVA4400 performance white paper 4AA1-8473ENW&lt;BR /&gt;&lt;BR /&gt;I have seen different ITRC posts suggesting a general estimation of 170-200 IOPS for 15K drives and 120-150 for 10K drives. &lt;BR /&gt;&lt;BR /&gt;I am trying to determine a performance baseline of an EVA and to know whether is overloaded or reaching max performance capacity with the current configuration. &lt;BR /&gt;&lt;BR /&gt;EVA4400 w/ dual controllers (09534000 firmware)&lt;BR /&gt;4GB total cache &lt;BR /&gt;2x Embedded 8GB switches&lt;BR /&gt;24x 450GB 15k &amp;amp; 10x 146GB 15K drives.</description>
      <pubDate>Thu, 11 Nov 2010 21:02:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712341#M46805</guid>
      <dc:creator>Xavi.e.r</dc:creator>
      <dc:date>2010-11-11T21:02:01Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712342#M46806</link>
      <description>Xavier&lt;BR /&gt;&lt;BR /&gt;Have you seen this support document?&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01685240" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01685240&lt;/A&gt;  &lt;BR /&gt;&lt;BR /&gt;I think together with the "A tactical approach to performance problem diagnosis" paper you referenced above you do have the info you need to get it sorted out. &lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 12 Nov 2010 07:27:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712342#M46806</guid>
      <dc:creator>Peter Mattei</dc:creator>
      <dc:date>2010-11-12T07:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712343#M46807</link>
      <description>See e.g. this thread:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1289562717213+28353475&amp;amp;threadId=1262271" target="_blank"&gt;http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1289562717213+28353475&amp;amp;threadId=1262271&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 12 Nov 2010 11:53:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712343#M46807</guid>
      <dc:creator>Mikko Niskanen_1</dc:creator>
      <dc:date>2010-11-12T11:53:31Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712344#M46808</link>
      <description>Thanks for the input.&lt;BR /&gt;Now, should I assume that the 120 and 170 IOPS per disk applies the same way when having VRAID 1,5,6 or how do I figure it out?&lt;BR /&gt;&lt;BR /&gt;Also, about the read and write latencies, should I consider them individually each host port on the EVA or should I do a sum of the  reads and a sum of the writes (EVA4400 has 4 ports: 2 ports per controller)&lt;BR /&gt;&lt;BR /&gt;I did a capture with evaperf for a few days, using tlviz, I see in the array an average of 3000 IOPS (total req/s)  and peaks on the 6000 IOPS. I see each host port very similar, the read latency averages 20-25ms and write latency 8-16ms. The latencies are over the numbers that HP recommends but the IOPS within the limits from the 5780 max calculated IOPS (2 disk groups, 1 with 24 450GB 15K and the 2nd 10 146GB 15K (1 vraid 5 and the rest vraid6) . Is this still an indication that EVA is overloaded or what other counters should I take in consideration? I am kinda confused here. Thanks</description>
      <pubDate>Fri, 12 Nov 2010 22:08:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712344#M46808</guid>
      <dc:creator>Xavi.e.r</dc:creator>
      <dc:date>2010-11-12T22:08:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712345#M46809</link>
      <description>The 120 and 170 IOPS are the backend performance numbers per disk you will find in EVAPerf. &lt;BR /&gt;Depending on the vRaid level these will be reached with more or less front-end IO.&lt;BR /&gt;&lt;BR /&gt;Pure reads are equal for all vRaid levels. &lt;BR /&gt;&lt;BR /&gt;Example for 1000 IOPS random front-end writes:&lt;BR /&gt;on vRaid1 this will caues 2000 back-end IOs&lt;BR /&gt;on vRaid5 this will cause &amp;gt;2000 back-end IOs&lt;BR /&gt;- Read the original data and parity block (two requests)&lt;BR /&gt;- Calculate the new parity block&lt;BR /&gt;- Write the new data and parity block (two requests)&lt;BR /&gt;&lt;BR /&gt;For vRaid 6 it will be even more.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 12 Nov 2010 22:27:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712345#M46809</guid>
      <dc:creator>Peter Mattei</dc:creator>
      <dc:date>2010-11-12T22:27:32Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712346#M46810</link>
      <description>Aye,&lt;BR /&gt;&lt;BR /&gt;If it is IOPS you're after, i.e. for an OLTP-style database use:&lt;BR /&gt;&lt;BR /&gt;- As many 15k disks as you can afford&lt;BR /&gt;- All disks to one disk group&lt;BR /&gt;- Total # of disks divisible by eight i.e. 8, 16, 24, 32,...&lt;BR /&gt;- Use only vRAID-1&lt;BR /&gt;- check SCSI command queue length&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Suggested reading EVA Best Practises docu:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA2-0914ENW.pdf" target="_blank"&gt;http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA2-0914ENW.pdf&lt;/A&gt;</description>
      <pubDate>Mon, 15 Nov 2010 10:12:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712346#M46810</guid>
      <dc:creator>Mikko Niskanen_1</dc:creator>
      <dc:date>2010-11-15T10:12:52Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712347#M46811</link>
      <description>Thanks for the responses. Now based on the previous info I included in the post above, Should the latencies really be under the those numbers (less than 5ms for write and 15ms for reads)? Would these latencies mean that there's something that needs to be done to reduce them ? if so what would it be? more drives? &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Nov 2010 13:55:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712347#M46811</guid>
      <dc:creator>Xavi.e.r</dc:creator>
      <dc:date>2010-11-15T13:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712348#M46812</link>
      <description>For Oracle, latencies of x &amp;lt; 10ms are okay, 10 ms &amp;lt; x &amp;lt; 20ms are warning signs and latencies x &amp;gt; 20 ms are not good, you're about to hit performance ceiling.&lt;BR /&gt;&lt;BR /&gt;If you check Fig 1 in &lt;A href="http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-8473ENW.pdf," target="_blank"&gt;http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-8473ENW.pdf,&lt;/A&gt; the read performance slopes nicely but you should be concerned if you have heavy writes, then you could hit a performance wall. Depends on your read/write ratio, if it's mostly reads, then 4400 will do good, but if you experience high write latencies over a long period (i.e. apart from occasional spikes), then you're in trouble.</description>
      <pubDate>Mon, 15 Nov 2010 14:02:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712348#M46812</guid>
      <dc:creator>Mikko Niskanen_1</dc:creator>
      <dc:date>2010-11-15T14:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712349#M46813</link>
      <description>Hey Xavier,&lt;BR /&gt;&lt;BR /&gt;I've spent the last few weeks doing just what your looking at and have written a tool. If you can get a perfmon log to me I reckon I could spot any performance bottle necks in about 10 minutes.&lt;BR /&gt;&lt;BR /&gt;I'm interested in testing the tool on other peoples machine's perflog data, so we'd both get something out of it.</description>
      <pubDate>Wed, 24 Nov 2010 19:10:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712349#M46813</guid>
      <dc:creator>McMac</dc:creator>
      <dc:date>2010-11-24T19:10:37Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712350#M46814</link>
      <description>Hey McMac&lt;BR /&gt;Thanks for the offering, I have a evaPerf capture that it's about raw 650MB/zipped 15MB.&lt;BR /&gt;&lt;BR /&gt;Let me know what do I need to do and what will your tool will do as well.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Wed, 24 Nov 2010 20:41:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712350#M46814</guid>
      <dc:creator>Xavi.e.r</dc:creator>
      <dc:date>2010-11-24T20:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712351#M46815</link>
      <description>It produces charts with an overview of latency, throughput etc.&lt;BR /&gt;&lt;BR /&gt;It also produces performance and utilization graphs for all element of the EVA, from physical discs to LUNS to ports including mirror port activity. And it identifies LUNS that are initiating proxy reads or writes and displays this traffic.  Other parts show the busiest LUNs and even busy physical discsâ ¦.&lt;BR /&gt;&lt;BR /&gt;I need to re-build it a bit as itâ  s only written for a single disk group, wonâ  t take long. Iâ  ll setup an FTP location this evening and let you know.&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Nov 2010 11:50:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712351#M46815</guid>
      <dc:creator>AlecMac</dc:creator>
      <dc:date>2010-11-25T11:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712352#M46816</link>
      <description>I'm McMac by the way :) I couldn't remeber my login from my home PC</description>
      <pubDate>Thu, 25 Nov 2010 11:51:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712352#M46816</guid>
      <dc:creator>AlecMac</dc:creator>
      <dc:date>2010-11-25T11:51:29Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712353#M46817</link>
      <description>Aye, nice sneak peek McMac! I've been having thinking to do the same thing with evaperf output. &lt;BR /&gt;&lt;BR /&gt;Any chance of sharing the effort, please?</description>
      <pubDate>Thu, 25 Nov 2010 13:33:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712353#M46817</guid>
      <dc:creator>Mikko Niskanen_1</dc:creator>
      <dc:date>2010-11-25T13:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712354#M46818</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;if anyone wants to ftp to 82.68.229.118 , username and password is perfmon, I'll run the report and post back here.</description>
      <pubDate>Thu, 25 Nov 2010 19:24:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712354#M46818</guid>
      <dc:creator>McMac</dc:creator>
      <dc:date>2010-11-25T19:24:00Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712355#M46819</link>
      <description>McMac, that ftp site seems to be done.</description>
      <pubDate>Mon, 29 Nov 2010 16:39:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712355#M46819</guid>
      <dc:creator>CLEB</dc:creator>
      <dc:date>2010-11-29T16:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712356#M46820</link>
      <description>Hi CLEB,&lt;BR /&gt;&lt;BR /&gt;the firewall is open now.  &lt;BR /&gt;&lt;BR /&gt;Just to confirm, the tool analyses EVA perf logs, generated by the command;&lt;BR /&gt;&lt;BR /&gt;e.g&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;evaperf all -csv -cont 10 -dur 7200 -ts2 -sz 5000-xxxx-xxxx-xxxx &amp;gt; c:\perf_bench.csv&lt;BR /&gt;&lt;BR /&gt;The variables are:&lt;BR /&gt;&lt;BR /&gt;-cont     frequency of snapshot (seconds)&lt;BR /&gt;-dur       duration of capture (seconds)&lt;BR /&gt;-sz          wwn name of eva&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Nov 2010 10:03:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712356#M46820</guid>
      <dc:creator>AlecMac</dc:creator>
      <dc:date>2010-11-30T10:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712357#M46821</link>
      <description>Hey AleMac/McMac,&lt;BR /&gt;I am trying to put the evaperf file in your ftp but I get 550 eva.7z: Forbidden filename&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Nov 2010 13:46:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712357#M46821</guid>
      <dc:creator>Xavi.e.r</dc:creator>
      <dc:date>2010-11-30T13:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 performance documentation</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712358#M46822</link>
      <description>Hi Xavier,&lt;BR /&gt;&lt;BR /&gt;I've enabled unicode support. No idea if it will help...&lt;BR /&gt;&lt;BR /&gt;If not I'll get another method. Other people have used it OK, so I hope it works for you.</description>
      <pubDate>Tue, 30 Nov 2010 15:27:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-performance-documentation/m-p/4712358#M46822</guid>
      <dc:creator>AlecMac</dc:creator>
      <dc:date>2010-11-30T15:27:45Z</dc:date>
    </item>
  </channel>
</rss>

