What Live Optics collects, and what it quietly does not
First in a short series on the tool everyone runs before a storage or platform proposal. Knowing the shape of the data is the difference between a sizing and a guess.
Farid’s Angle farids.dev · Algiers
I size data centre and AI platforms for a living, in Algiers. These are the notes I wish someone had handed me before the meeting: what the numbers really say, where the vendor tool is quietly helping itself, and what breaks in month four.
First in a short series on the tool everyone runs before a storage or platform proposal. Knowing the shape of the data is the difference between a sizing and a guess.
Second in the series. The collection window is the single input that most often invalidates a sizing, and it is the one nobody negotiates.
Third in the series. IOPS, block size, read/write mix and the compression estimate — what each one is actually measuring, and where the sizing goes wrong.
Last in the Live Optics series. The arithmetic between the data and the recommendation is where every argument happens, and it is almost always invisible.
Most people open the VMware renewal at the total. That number is the last thing you should look at, and by then you have already lost the argument.
It is not a faster NAS. The architectural difference is that clients talk to many storage servers at once, and almost every operational surprise follows from that.
Every parallel file system is sold on GB/s. Almost every one that disappoints in production is disappointing because of operations per second on small files.
Two numbers control whether your parallel file system behaves like dozens of servers or like one. Most sites never change them.
The performance is not the issue. The issues are upgrades, client evictions, one slow target poisoning everything, and the fact that it assumes you employ someone who knows it.
GPFS by its older name. Technically excellent, operationally more forgiving than Lustre, and sold in a way that requires you to read carefully.
GPUs, fabrics, power, and the parts nobody sizes.
Things I actually built and what broke.
VMware, AHV, KubeVirt, and life after the renewal.
Arrays, protocols, latency, and honest numbers.
Where it pays off and where it quietly does not.
Recovery, immutability, identity, exposure.
Kubernetes, OpenShift, and the operating model.