On Thu, Dec 17, 2009 at 1:49 PM, Daryl G. Jurbala <span dir="ltr"><<a href="mailto:daryl@introspect.net">daryl@introspect.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
On Dec 17, 2009, at 4:29 PM, nick hatch wrote:<br>
<br>
><br>
> Or, maybe there's something else going on. Many ESXi users do use the local datastores, so maybe that's where the "enterprise has less timing issues" perception comes from -- if you're paying for licensing, you're probably using a SAN and vice versa. If using local datastores affects network I/O, "enterprise" users might sidestep this issue entirely.<br>
<br>
</div>Timing issues have nothing to do with what datastore type you are using. They have everything to do with how VMWare handles interrupts.<br></blockquote><div><br>Indeed, that makes sense, and is what I was getting at. However, if you have a local datastore, you're generating hardware interrupts on the box above what one would see with remote storage, no? It would seem to make sense that under heavy load, when interrupts matter, not running a RAID controller of your own could be an advantage. Gigabit NICs have sane methods of dealing with interrupts, like coalescence.<br>
<br>I could be wrong, however. My point was just an attempt to explain why someone might think timing issues are related to "non-enterprise" VMWare.<br><br>-Nick<br></div></div>