Re: Irrelevant?
"If it's that a useful feature why on earth wouldn't it be added to KVM/QEMU sharpish? Who are you to dismiss something so out-of-hand?"
I don't see any talk about devs implementing this feature on KVM or QEMU. Implementing this isn't just adding an enable_nvme_tiering setting somewhere but will take a lot of development and testing resources.
If the KVM developers find this a useful feature, they might implement it. But talking about months is pure fantasy.
"Oh goody, more time for you to get thoroughly addicted/over-reliant on the technology so that Broadcom can REALLY make you squeal when it comes to renewals.
People have been reliant on VMware for couple of decades because it has been the best-in-class. And it still is. Moving from VMware to any other is a downgrade in features, ecosystem, maturity.
If you rely on Nutanix, HPE, IBM/RedHat or other paid virtualisation tech, they are equally looking to extract all loose money from their clients as well. Sorry to tell you this.
Moving to any other hypervisor environment is always a chore, why would it be harder in the future? Some of VMware competitions is making the move easier these days.
"Seriously what the hell are you actually doing that needs you to CapEx 1TB of RAM, yet you can't afford it?"
That was for a single server. Times 10 or 100 for some companies. Even the bigger companies balk at some point. If you can save thousands or millions with memory tiering - just like you can/could with storage tiering - with minor performance loss, why would you NOT do it?
"I've worked for plenty of clients and companies that have ended up with more than that amount of RAM in play, but it's always been through incremental expansion."
1TB is peanuts where I work. That was an example of how hardware refreshes these days are very expensive compared to year ago.
"Anything more "spiky" has been done in the cloud to prove the concept first before justifying massive CapEx."
Can't work with cloud because of latencies, regulation and other reasons.