3 ms·
Quick aside: does ESXi still impose too much overhead to move a compile farm onto VMs? A friend of mine tested it 3 years ago and it was something like 300% sl
by rch 15y ago
Quick aside: does ESXi still impose too much overhead to move a compile farm onto VMs?
A friend of mine tested it 3 years ago and it was something like 300% slower (no idea about the disk config, but he's a smart guy). It would have been worth it at anything under about a %50 hit...
- Spyplane 15y agoWe tested it at my last job maybe 5 months ago and it was a complete failure. Granted we didn't spend a lot of cycles on it, but we saw how slow it was and went back to native hardware pretty quick.
- absconditus 15y agoWhat exactly would be gained by using VMs, assuming that there were no performance problem?
- Joeri 15y agoTwo reasons: - Easy migration between hardware configurations of a running system. - Snapshots to revert quicker after a failed upgrade / change. (Typically in addition to traditional backups.)
- tedunangst 15y agoThe boss gets to put "lead the conversion to a virtualized environment" on his resume. True story.
- rch 15y agoMy case was for a heterogeneous build environment, where separate environments needed to be maintained for different developer groups. It would have been a good fit for VMs.. except for the performance.