Do they belong to you? Claim these comments.
Keith
Is this you? Claim Profile »
6 months ago
in Mission Critical App Nears Uptime Record on Mike D's Virtualization Blog
I worked for the "1516 day" company up until March of this year :-) Patching and keeping hosts up to date is certainly the best practice but as you said in large environments things can turn slow for certain reasons.. we went from 2.01 to 2.5.1. to 2.5.4. Once we began down the 3.01/3.02 train we commenced patching with a bit more frequency. That particular host was rock solid (DL580G2) running 2.01.
1 reply
Mike DiPetrillo
Thanks for the insight, Keith. It's always nice to have the customers commenting to validate things. It's a shame we can't get more case studies with customer names out there but at least we can anonymously share information this way. :)
10 months ago
in HP Proliant DL785 G5 rocks at VMWare on Bladewatch
really depends on the environment your on and how high you want to stack workloads. i've setup 16 node clusters with a mixture of 2 socket and 4 socket quads (Intel) and would have used 8 sockets if Intel still made them. I started way back with a mix of DL580G2's and DL740's w ESX 2.x and had great success. More procs; more places to schedule VM's and they can get the performance attention they ask for.
11 months ago
in thehypervisor.com reports VMware Workstation faster than Hyper-V on vm /etc
that is a pretty pointless post on their part. What is the point in timing the installation routine; specifically when at that point all the devices are emulated. Hyper-V performs best with the Integration Services installed in each VM. As does VMware with the tools installed.