<?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 How many VM's per datastore in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/how-many-vm-s-per-datastore/m-p/6983919#M1045</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was reading this post regarding how many vm's to store in a datastore &lt;A href="https://community.hpe.com/thread/1887"&gt;How big are your VMFS datastores/how many VMs?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the 10-15-20 rules seems fairly well tried and tested, so it leads me to wanting to understand what is considered high, medium &amp;amp; low I/O. It seems fairly fundamental to understand this when designing a datastore layout.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Nathan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 30 Jul 2015 09:43:24 GMT</pubDate>
    <dc:creator>nathanulph41</dc:creator>
    <dc:date>2015-07-30T09:43:24Z</dc:date>
    <item>
      <title>How many VM's per datastore</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/how-many-vm-s-per-datastore/m-p/6983919#M1045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was reading this post regarding how many vm's to store in a datastore &lt;A href="https://community.hpe.com/thread/1887"&gt;How big are your VMFS datastores/how many VMs?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the 10-15-20 rules seems fairly well tried and tested, so it leads me to wanting to understand what is considered high, medium &amp;amp; low I/O. It seems fairly fundamental to understand this when designing a datastore layout.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Nathan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jul 2015 09:43:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/how-many-vm-s-per-datastore/m-p/6983919#M1045</guid>
      <dc:creator>nathanulph41</dc:creator>
      <dc:date>2015-07-30T09:43:24Z</dc:date>
    </item>
    <item>
      <title>Re: How many VM's per datastore</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/how-many-vm-s-per-datastore/m-p/6983920#M1046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That whole purpose of limiting the number of VMs per datastore is to reduce the induced latency from queueing. Each ESX host by default has a queue depth of 32 per VMFS datastore. If your storage averaged 5ms latency for all IOs then the maximum theoretical IOPS before inducing latency would be: (1 host) * (32 queue depth) * (1,000 ms / 5ms average latency) = 6,400 IOPS before inducing latency from queueing. So if we had 10 high IO VMs this would equate to about 640 IOPS per VM. Giving each VM the equivalent to a stand alone host with 4 - 15k disk RAID. Thusly having 20VMs per datastore would reduce this to a potential of 320 IOPS per VM. These numbers are per host so as you add hosts you can have more than 10-15-20 per VMFS datastore so long as they are evenly spread across the ESX hosts in the cluster.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jul 2015 15:00:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/how-many-vm-s-per-datastore/m-p/6983920#M1046</guid>
      <dc:creator>aherbert23</dc:creator>
      <dc:date>2015-07-30T15:00:11Z</dc:date>
    </item>
  </channel>
</rss>

