VMware Back-Pedals On vRAM Scheme, Back To Per-Socket Pricing 70
Last year VMware introduced a complex pricing scheme based on the size of the memory associated with each virtual machine instance. New CEO Pat Gelsinger announced this week that this system (which he described as "a four letter word") has been deprecated, and VMware is back to more straightforwardly charging per physical processor. Adds reader hypnosec: "Pricing hasn't been announced yet but a file [PDF] present on VMware's site does give an indication about the new pricing."
Update: 08/28 17:18 GMT by S : Updated the headline and summary to reflect that the price is per processor, not per core.
Update: 08/28 17:18 GMT by S : Updated the headline and summary to reflect that the price is per processor, not per core.
Isn't that per socket, not per core? (Score:5, Informative)
The summary says this:
VMware is back to more straightforwardly charging per physical processor core.
But I think they mean per socket. (or maybe per physical processor, but not per core)
Re:I used to love VMware (Score:4, Informative)
When as far as I could see, ESXi got worse from 4.1 to 5
In what way? Better HA, datastore heartbeating, removal of the 2TB-per-datastore limit, DPM, better ways of dealing with RAM contention (page sharing)...
there are a LOT of ways ESXi got better in version 5. Only regression Im aware of is that the VUM no longer does guest updates, but TBQH who really cares? Just use WSUS or your package manager in Linux.