We have been running HyperV VMs for a few years now as development machines, as it is a quick and easy way to manage, update and replace enviroments.
Of late Visual Studio, with upwards, if not more than, 50 projects per solution has become unresponsive much of the time, losing our team hours of development a week.
A contractor recently argued that VMs are notoriously bad at file IO and a terrible solution for Dev environments, and we should be running images on PCs, installed with software like BartPE or Ghost (excuse my dated references, it's been a while since I played in that space) to allow for the quick SOE updating we were wanting with VMs.
I was wondering if this is really is a limitation of VMs, and, if so, are there any sources available I could use to convince the budget owning management of this.
0 Answers