HN Explorer

Ask HN: Is there a website that tracks excessive writes to SSDs in OS/app betas?

31 points by amichail ↗ HN
If not, why not?

That way, people can choose whether they want to install various software betas based on how much SSD wear they are willing to accept.

And since this data would be made public and available in one place, software developers would be more careful about excessive logging in their betas.

12 comments

[ 0.25 ms ] story [ 27.3 ms ] thread
CharlesW
> If not, why not?

At least on Apple devices, this is not something anyone has to worry about.

For example, on my 2022 Mac Studio daily driver, on 24/7, DriveDx (https://binaryfruit.com/drivedx) reports my SSD lifetime left at 94%.

(I'm aware of the February 2021 "wear-gate" scare involving the first M1 Macs. This turned to be incorrect SSD-wear reporting.)

[dead] neya
[flagged]
tomhow
Please don't act like a jerk on HN. There are articles and comments criticizing Apple all the time and it's fine.
neya
You of all the people should and would know that the slightest criticism of Apple is rejected here, not based by merit of the argument, but for simply endorsing the viewpoint that Apple can be evil too. I'm sure mods have tools and stats to see all this and you probably see it too, but you be you.
tosti
Just configure wear leveling in your storage layer. FDE may be the easiest way ti do it. Writes will be done linearly in circular fashion. That makes it difficult to delete stuff, but with encryption it's moot.
markhahn
devices already do wear management.

at most, you should configure your system and OS to give them a chance. for instance, being 100% full all the time is just bad. use TRIM and log SMART metrics.

markhahn
why do you think this is a function of betas? or even of OS or app versions?

I guess you've been burned, or are worried about being burned, by some software that generated excessive writes? I think you need to describe that first, since this is a rare phenomenon.

which is probably why there isn't some kind of downdetector infra tracking it.

you know you can access smart counters on any OS, right?

justsomehnguy
If you are not using bottom of a barrel and you are not writing 4K HD 3H mkv every day then you wouldn't have a problem even with a 0.3 DPWD drive of a sufficient capacity.
KomoD
> 0.3 DPWD

What does this mean?

justsomehnguy
Drive Write Per Day (typo in my previous comment)

From the horse mouth: https://www.kingston.com/en/blog/servers-and-data-centers/un...

0.3 DWPD is for the cheapest ones but even for them you would never exhaust the flash resource in a common home usage.

To give you an idea:

a 120GB drive with 0.3 DWPD "allows" you to rewrite 120 x 0.3 = 40GBytes a day for 3 years straigth, which is 280GB/week or 1200GB/month.

for a 1TB drive it would be 300GB/day, 2100GB/week, 9000GB/month.

embedding-shape
I feel like the only responsible thing is to have a home network with at least one persistent device running 24/7 with large storage for local backups of things, and ideally a E2E cloud backup of the same thing. With this, comes the possibility of using things like Grafana+Prometheus to monitor your personal computer/workstation as well. This is what I've done, together with alerts from various things, and since the recent "excessive writes by codex" issue, also alerts if there is obsessive writing over hours long period from any process on my workstation. Luckily I wasn't hit by the Codex issue myself, but certainly made me consider the issue more generally so, happy accidents :)