Slow data movement is rarely a line item — so it hides. But it bills every day: idle machines you pay for by the hour, people waiting on data, blown migration windows, and bandwidth you provision but never fill. An AI factory feels it sharpest — GPUs billing by the hour while a multi-petabyte training set crawls in. Here is where it adds up, and how to put a number on it.
An accelerator stalled on a checkpoint or dataset still costs you by the hour. In an AI factory, even a 15% data stall runs into the millions a year.
Price idle machines →A researcher waiting on a sequencing run or an analyst on the overnight batch is a cost too — and in many fields the bigger one. It is salary spent watching a progress bar.
Price the wait →Until a migration cuts over, you pay for both the old and new environments at once. A slow mover stretches that overlap from days into weeks.
Cost a slow cutover →A 100 Gbps circuit filled to 30% is a 30 Gbps circuit bought at full price. Single-stream tools leave most of your pipe — and its bill — idle.
Find wasted bandwidth →Idle-machine cost = machines × cost per hour × the share of time they wait on data, across a year. Add the people idled on data the same way, and the bandwidth you pay for but cannot fill. Our calculators do it with your figures and build a downloadable business case — with a pitch you can take to your stakeholders.
When data moves at line rate — the ~90%+ the Zettar zx Appliance realizes — machines stay fed, people stop waiting, migration windows collapse, and the bandwidth you already pay for finally does work. Proven: 1 PB in 29 hours at 96% utilization with SLAC and the U.S. DOE.
It is the sum of idle machines that bill while they wait, people idled on data, migrations that double-run for weeks, and bandwidth you pay for but never fill. At scale it commonly reaches seven figures a year; our calculator puts a number on it for your environment.
Idle-machine cost = machines times cost per hour times the share of time they wait on data, across a year; add people the same way, plus the bandwidth you cannot fill. The Zettar cost calculator does it with your figures and builds a downloadable business case.
By moving data at line rate (about 90%+), so machines stay fed, people stop waiting, migration windows collapse, and the bandwidth you already pay for does work. Proven: 1 PB in 29 hours at 96% utilization with SLAC and the U.S. DOE.
Run the numbers on your environment, then let us prove what line rate recovers — measured, not estimated.