At what, 10 tokens per hour? These disk swapping methods all have the same drawbacks - kill your drive early, and slow as hell.
At what, 10 tokens per hour? These disk swapping methods all have the same drawbacks - kill your drive early, and slow as hell.
It says very prominently in the post: 4.5-5t/s for 80b on an M5
Isn’t it only writes that kill drives?
There's read disturb on SSDs, enough reads will eventually force controller to rewrite the cell and it's neighbours.
Practically if you're not streaming weights 24/7 from a full SSD, then it shouldn't be a problem.
Read disturb ought to be quite rare, especially on a fresh drive that was written only once or a handful of times (WORM-like usage). Practically, it's not likely to be an issue even with very heavy read workloads.
Hm, I asked 5.6 Sol to calculate/research and it came up with way less optimistic lifespan than Gemini (that I've asked last year).
It claims that each individual page read induces read disturb across whole block. And references https://arxiv.org/pdf/2501.02517 that tested Samsung 3D TLC and found ~518K sequential page reads in a block to be ECC threshold (although it's unclear how they got 518K number -- e.g. is it single worst chip they've tried? authors brings up 160 chip sample size later on).
With 7704 pages in a block that's only ~70 sequential block reads till data is lost and to retain data controller would have to refresh block fair bit earlier.. basically it gives modern 3D TLC SSD lifespan measured in months (1TB drive 24/7 sequential reads at 5GB/s).
Yeah, that's why most of these comments seem weird to me.
Yes for NAND, and I suppose nobody is using mechanical hard drives for this.
Am I the only one that has no flash lifetime anxiety? I still have drives from more than a decade ago that keep on chugging fine.
I remember the time spinning rust was the only option and reliable they weren't. In 30 years of computing I have had more than ten hdds and zero ssds die.