I was asking about the use can becase it sounded like the VM that needed the IOPS is just going to run slower and take longer.
There is another way to adress the IOPS. You can do Server Side Cacheing with software and some FLASH and get 100K+ IOPS. Then you would not have to limit the VM's performanace.
WWW.SanDisk.com/FlashSoft-Connect<http://www.sandisk.com/FlashSoft-Connect>
http://www.youtube.com/watch?v=6eDTqLcewGY
Solutions Architect | SanDisk / FlashSoft Software
From: Wiley Wimberly <communities-emailer@vmware.com>
To: jrosco@yahoo.com
Sent: Thursday, March 14, 2013 3:16 PM
Subject: Re: Limiting IO per VM New message: "Limiting IO per VM" Re: Limiting IO per VM
VMware Communities<http://communities.vmware.com/index.jspa>
Limiting IO per VM
reply from Wiley Wimberly<http://communities.vmware.com/people/wwimberly> in VMware vSphere™ Storage - View the full discussion<http://communities.vmware.com/message/2211032#2211032>
We are trying to prevent a "noisy neighbor" VM from generating excessive IO that increases latency and negatively impacts the other VMs that share that datastore.
Reply to this message by replying to this email -or- go to the message on VMware Communities<http://communities.vmware.com/message/2211032#2211032>
Start a new discussion in VMware vSphere™ Storage at VMware Communities<http://communities.vmware.com/choose-container!input.jspa?contentType=1&containerType=14&container=3036