<?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 esxi 5.5+ host cache best practices? in Array Performance and Data Protection</title>
    <link>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982464#M222</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I migrated from a HP EVA array to a Nimble CS300 a few months ago, at start I had host caching configured for our esxi hosts as they had mirrored SSDs installed in them. My thinking is local SAS storage will be faster than navigating an HBA to get to the Nimble - am I right in that? Has anyone played with host caching and Nimble - seeing what effect turning it on an off has on performance and utilization on the array?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Aug 2015 15:47:42 GMT</pubDate>
    <dc:creator>PeterMu</dc:creator>
    <dc:date>2015-08-17T15:47:42Z</dc:date>
    <item>
      <title>esxi 5.5+ host cache best practices?</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982464#M222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I migrated from a HP EVA array to a Nimble CS300 a few months ago, at start I had host caching configured for our esxi hosts as they had mirrored SSDs installed in them. My thinking is local SAS storage will be faster than navigating an HBA to get to the Nimble - am I right in that? Has anyone played with host caching and Nimble - seeing what effect turning it on an off has on performance and utilization on the array?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Aug 2015 15:47:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982464#M222</guid>
      <dc:creator>PeterMu</dc:creator>
      <dc:date>2015-08-17T15:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: esxi 5.5+ host cache best practices?</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982465#M223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Swap caching or Virtual Flash (which became available in 5.5)?? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Nov 2015 03:26:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982465#M223</guid>
      <dc:creator>tmoore106</dc:creator>
      <dc:date>2015-11-24T03:26:58Z</dc:date>
    </item>
    <item>
      <title>Re: esxi 5.5+ host cache best practices?</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982466#M224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ah I meant swap caching originally. I would be curious though if anyone has tested with vFlash though if there is a performance advantage&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Nov 2015 19:36:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982466#M224</guid>
      <dc:creator>PeterMu</dc:creator>
      <dc:date>2015-11-24T19:36:43Z</dc:date>
    </item>
    <item>
      <title>Re: esxi 5.5+ host cache best practices?</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982467#M225</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'd be curious to see some input on this as well.&amp;nbsp; What type of performance boost were you looking for?&amp;nbsp; The latency to the array is already so low I can't see the local ssds doing much.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Feb 2016 15:44:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982467#M225</guid>
      <dc:creator>tomatthe119</dc:creator>
      <dc:date>2016-02-25T15:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: esxi 5.5+ host cache best practices?</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982468#M226</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure how much vFlash improved with vSphere 6, but with 5.5 the function is limited.&lt;/P&gt;&lt;P&gt;It is not a dynamic resource. You can’t just put 2 TB SSDs in the server and say use them for read cache.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have to dedicate some space to each VM which makes it rather... well not complex... but time consuming.&lt;/P&gt;&lt;P&gt;&lt;IMG alt="clipboard.jpg" class="jive-image image-1" src="https://community.hpe.com/legacyfs/online/2804_clipboard.jpg" style="height: auto; width: auto;" /&gt;&lt;/P&gt;&lt;P&gt;Also what happens if you move that VM to a different server and on that servers is not enough vFlash capacity left for this VM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also have to agree with Travis!&lt;/P&gt;&lt;P&gt;A good designed network (10GBit) should add well below 20 microseconds of latency.&lt;/P&gt;&lt;P&gt;I don't think there will be a notable difference whether the IO comes from local SSD or a Nimble SSD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pierre&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jul 2016 19:25:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/esxi-5-5-host-cache-best-practices/m-p/6982468#M226</guid>
      <dc:creator>pflammer23</dc:creator>
      <dc:date>2016-07-26T19:25:41Z</dc:date>
    </item>
  </channel>
</rss>

