Eco4Cloud Workload Consolidation vs. VMware ESXi

Eco4Cloud is well suited in VMware farms that have standard VM deployments, especially with small VMs, with nothing blocking vMotion and hardware fully compatible with IPMI 2.0 (minimum). It doesn't work well if many VMs are nodes in a Microsoft cluster because they would be unmovable and therefore their host would never be put in stand-by mode. If every host in the cluster has at least one guest VM that is a node of a Microsoft cluster, no host in the cluster will ever be put in stand-by mode.

If you're looking for the industry standard in server virtualization, I would recommend ESXi. After decades of expertise in the field, VMware continues to provide a strong product, production-ready, with an easy-to-learn interface that allows for quick management along with less costly upfront onboarding and training. Grab the free personal-use license and install in your homelab to start!

Incentivized

• It consolidates workloads in VMware clusters using an algorithm that seems to work better than VMware DRS. It keeps headroom for workload peaks and to withstand the number of host failures set for the cluster in vCenter.
• If the workload is very variable, Eco4Cloud will not continuously turn a host on and off but it will settle to keep the host running. It sort of "rightsizes" the cluster keeping only the right number of hosts running. This is another main difference when comparing Eco4Cloud with VMware DRS/DPM which strictly follows the workload and sometimes isn't fast enough in turning on the hosts when the workload is ramping-up.
• To do a good job Eco4Cloud needs to analyze the hosts and the VMs. Therefore, the troubleshooting component of Eco4Cloud can figure out if there are problems in the configuration of the hosts (e.g. vMotion settings). It can also determine if a VM is stuck and can't vMotion (e.g. using the physical CD-ROM) or if it's oversized or undersized.
• Something Eco4Cloud has and others don't is a technology named Smart Ballooning. With Smart Ballooning Eco4Cloud recovers unused RAM from the VMs and gives it back to the host way before the host goes over the 94% RAM threshold. This allows us to reach higher levels of overbooking.

• Incredibly quick to deploy. Total installation time of less than five minutes
• Able to easily mount ISCSI storage devices to VMWare ESXi hosts within the GUI
• Allows you to run the product for free - if you stay under the physical core count (and with some reduced features)
• Incredibly stable software - we have not run into any issues that were a direct result of VMWare ESXi being at fault
• Very low hardware resources utilized to run this product

Incentivized

• It would be useful to have a version that works with OpenStack.
• It should be made compatible with VMware VSAN.
• It would be useful to have a version that works with hybrid clouds using the new "vMotion anywhere" or share nothing vMotion feature.

• There are some odd issues with VMware's virtualized network drive (VMXNET3). On occasion, after a reboot of a Windows-based VM the NIC will fail to bind properly and network access is unavailable until an admin intervenes by disabling/re-enabling the adapter. While it's possible that our environment is a contributing factor, this never happens on VMs using Intel E1000 emulation, only the paravirtual NICs.
• Logging is extensive but difficult to work with. VMware's solution is a product called Log Insight, which comes at additional cost. Fortunately this is somewhat mitigated by the extensive support documentation and robust user community, but in the heat of the moment obtaining the required detail can be a trying experience.

Incentivized

It is critical to our business, what started out as a way to do certain functions, it has now become core to ensuring our product is available to our customers and reducing our costs to operate and reduce our recovery time and provisioning servers. Their support is great and the costs to renew is reasonable.

Incentivized

The interface is fairly intuitive for most things, and the areas that are a little less obvious usually have fantastic documentation in the online knowledgebase. In 3-4 years of managing our ESXi hosts, I think that I have only opened 4-5 support cases for things that I could not figure out myself or find answers to on the website.

Incentivized

Without the need to patch the servers with bug fixes and enhancements we whave not experienced any downtime with VMware issues. Even the bug fixes and updates do not cause of downtime as we just migrate the servers to the opposite node and update the one and then move servers back. Very simple and painless.

Incentivized

We do not notice any difference between a physical and virtual server running the same workload. In fact we can scale quicker with the virtual server than we can with the physical.

Incentivized

I rarely ever need support for anything VMWare makes, but when I do, the documentation available just in the free community is generally enough. It's extensive and the community is truly robust and active. And if you have a myvmware account, you can get support for your owned products from VMWare support by the conventional case/ticket method

Incentivized

Jsut read and follow anything your storage provider may require to allow the integration of VMware with storage operations, outside of that VMware jsut works.

Incentivized

We compared the consolidation feature and we obtained exactly the same amount of servers in stand-by. The main difference was that Eco4Cloud turned off the unneeded hosts in 2 days while VMTurbo Operations Manager required one day per host. This behavior is caused by the different algorithms implemented by these two products. Compared to Eco4Cloud, VMware DRS/DPM was very aggressive (we tried it in vSphere 5.0). We haven't tested it with vSphere 6 yet.

While Hyper-V also can work very well and can have licensing benefits, it does rely on Windows in order to run. This isn't necessarily a bad thing, but it can add another layer of potential failure and might not be running on as low of a level as ESXi does. The footprint for Hyper-V can be smaller if the Desktop Experience isn't used for the hosts, but this is the default fashion that ESXi has been running for many years. VMware's support has always been stellar, and its documentation is phenomenal. Hyper-V can work as a virtual environment option, but ESXi has never let me down in any environment I have managed. I will continue standing by this product and prefer it over other options. It has proven itself time and time again over time as the defacto virtual environment hosting platform.

Incentivized

We started out with a two-server cluster and adding a third or fourth is very straightforward and simple with no issues. You just need to be aware of the size of your Vcenter Server to handle the workload, but still the resources needed is very minimal

Incentivized

• Eco4Cloud causes a reduction in power consumption both on old VMware clusters and especially on new ones.
• It also causes a delay in CapEx investments because you buy more hosts only when really needed.

• Positively, it has saved us time in spinning up new servers for the different departments in our company. It is easy for us to spin up virtual machines with VMware ESXi and deploy applications at the drop of a hat.
• Positively we are able to save space in our data closets as we no longer need to keep room for physical servers and workstations, allowing us to expand in other areas like networking equipment and physical backup solutions.
• It has moved our business forward as we are able to migrate old servers and static workstations in the virtual environment allowing us to easily keep an eye on older applications and update/backup easily through VMware ESXi management console.

Incentivized