Earlier quoted context omitted.
Its easy to do this when you have no strong competition, and don't care if you piss off your existing customers. The irony is they want to ride the new wave of public cloud computing, going so far as to sponsor development of a memory database (Redis), and then go and do something regressive like slapping a 24GB-per-CPU memory limit on their core product without a price decrease.
Wow, I never saw it that way. Brilliant move for the books though. But I guess if your box needs 24GB then you probably have cash no?
VMWare Screw Customers
11–20 of 93 posts
Re: VMWare Screw Customers
#12Earlier quoted context omitted.
Wow, I never saw it that way. Brilliant move for the books though. But I guess if your box needs 24GB then you probably have cash no?
To me, 24GB per cpu seems very low for a VM host.
Re: VMWare Screw Customers
#13Earlier quoted context omitted.
To me, 24GB per cpu seems very low for a VM host.
Really? Per 10-core cpu or per core?
Re: VMWare Screw Customers
#14On the original page's comments some people mention it might even be cheaper to buy hardware instead of licenses, anyone have a take on that? Example: a) 1 x Large Server + VMware licenses -or- b) N x Small Servers If b) is more cost-effective then VMWare definitely dropped the ball here...
Certainly smaller hosts with DR capability can be done for lower capital spend, but you need more capable admins to manage it. VMWare does that for you out of the box.
Re: VMWare Screw Customers
#15Re: VMWare Screw Customers
#16Re: VMWare Screw Customers
#17Earlier quoted context omitted.
To me, 24GB per cpu seems very low for a VM host.
Really? The standard host hardware for the place I work was 128gb/16 core for the longest time. Prior to that, it was 64g/8 core.. which did suffer of memory overcommit for a while. The 128/16 balances quite nicely. 128/16 leaves plenty of room for over a dozen reasonably sized VM's (8gb/2vcpu) without even approaching oversubscription of memory. Sure, if you want to go crazy and stack more than 15-20 VM's on a host…
But honestly, that's not the right way to think about the licensing. Sure, you need a license for each physical cpu, but beyond that you're just licensing for vRAM. So the real question is, is 24GB vRAM per license low.
Re: VMWare Screw Customers
#18Earlier quoted context omitted.
Its easy to do this when you have no strong competition, and don't care if you piss off your existing customers. The irony is they want to ride the new wave of public cloud computing, going so far as to sponsor development of a memory database (Redis), and then go and do something regressive like slapping a 24GB-per-CPU memory limit on their core product without a price decrease.
But the new wave of public cloud computing is not generally running VMWare's product, as it is too expensive; eg EC2 runs on Xen... they are doing better from the private cloud people who are less concerned about using commodity open source software.
Re: VMWare Screw Customers
#19On the original page's comments some people mention it might even be cheaper to buy hardware instead of licenses, anyone have a take on that? Example: a) 1 x Large Server + VMware licenses -or- b) N x Small Servers If b) is more cost-effective then VMWare definitely dropped the ball here...
Cheaper? Maybe -- but people like VMWare for the management interface and often the other addions like DRS/HA, vMotion, vStorage. Certainly smaller hosts with DR capability can be done for lower capital spend, but you need more capable admins to manage it. VMWare does that for you out of the box.
I.e., VMWare is usually a better deal, but just barely. Drives me insane.