![]() ![]() ![]() |
|
insane: Been playing with the ESXi 5.0 beta for some months now, seems like they have made a few nice tweaks , such as reducing the dependency on the VMA if you're using iSCSI storage.
Of course the host based replication for SRM is what I'm most looking forward to.
As far as vRAM is concerned we're quite quite lucky as we currently run 96GB with duel hex core CPUs with Ent Plus, so we're not affected by the new licensing at all. In fact with VSPP 3.0 it's actually cheaper than VSPP 2.0 overall.
I wouldn't want to run more than 48GB per socket anyway as CPU ready values begin to spike when you go past that, so although limiting for some, it's about right, even if it does remove the choice from the customer.
Zeon:insane: Been playing with the ESXi 5.0 beta for some months now, seems like they have made a few nice tweaks , such as reducing the dependency on the VMA if you're using iSCSI storage.
Of course the host based replication for SRM is what I'm most looking forward to.
As far as vRAM is concerned we're quite quite lucky as we currently run 96GB with duel hex core CPUs with Ent Plus, so we're not affected by the new licensing at all. In fact with VSPP 3.0 it's actually cheaper than VSPP 2.0 overall.
I wouldn't want to run more than 48GB per socket anyway as CPU ready values begin to spike when you go past that, so although limiting for some, it's about right, even if it does remove the choice from the customer.
TBH I think you guys are almost the exception in that regard though. Everyone I know is always thinking about maximizing RAM as so many VMs sit idle CPU wise.
I think VMware have based their pricing around what they think the ideal setup should be wheras in the real world a lot of their clients use the product for different reasons. It's not going to work for us so we will need to shift so will be interesting to see if this works for VMware
|
![]() ![]() ![]() |