<?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: Mirrorclone, performance impact in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/mirrorclone-performance-impact/m-p/4281787#M33528</link>
    <description>thx uwe</description>
    <pubDate>Tue, 07 Oct 2008 08:19:40 GMT</pubDate>
    <dc:creator>hpuserabc</dc:creator>
    <dc:date>2008-10-07T08:19:40Z</dc:date>
    <item>
      <title>Mirrorclone, performance impact</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/mirrorclone-performance-impact/m-p/4281785#M33526</link>
      <description>is there any performance impact when using mirrorclone ?&lt;BR /&gt;&lt;BR /&gt;could perfmon show the significant difference ?&lt;BR /&gt;&lt;BR /&gt;i would like to know the difference but it should based on data/numbers not merely theory.&lt;BR /&gt;&lt;BR /&gt;any advice on how to do the testing will be appreciated&lt;BR /&gt;&lt;BR /&gt;thx in adv&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Oct 2008 03:34:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/mirrorclone-performance-impact/m-p/4281785#M33526</guid>
      <dc:creator>hpuserabc</dc:creator>
      <dc:date>2008-10-07T03:34:34Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrorclone, performance impact</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/mirrorclone-performance-impact/m-p/4281786#M33527</link>
      <description>Sure there will be a performance impact - such actions are never free. Whether it is noticable for the end-user or can be absorbed by caching depends on many things (as usual ;-)&lt;BR /&gt;&lt;BR /&gt;We cannot give you an exact number (mirror cloning will cost you N% of X) as every array is different. EVAperf can give you information about latencies down to the individual virtual disk. No offence meant, but I think you need to get the numbers from your own installation.&lt;BR /&gt;&lt;BR /&gt;Set up a virtual disk, wait until the initial zeroing has completed and run some tests with "iometer". Set up a mirror-clone, wait until the initial copy has completed and run the same tests. Fracture the mirror-clone (stop the continuous sync, but keep a differential bitmap) and run some more tests (should include writes).</description>
      <pubDate>Tue, 07 Oct 2008 04:10:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/mirrorclone-performance-impact/m-p/4281786#M33527</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-10-07T04:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrorclone, performance impact</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/mirrorclone-performance-impact/m-p/4281787#M33528</link>
      <description>thx uwe</description>
      <pubDate>Tue, 07 Oct 2008 08:19:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/mirrorclone-performance-impact/m-p/4281787#M33528</guid>
      <dc:creator>hpuserabc</dc:creator>
      <dc:date>2008-10-07T08:19:40Z</dc:date>
    </item>
  </channel>
</rss>

