On my personal computers I keep track of this and ensure nothing goes write-crazy.
On my work laptop though (M3 Pro, 1TB), I’m at ~70% health. Iirc the lifetime writes are at >700TB. I do develop on it, but a lot of it is due to the various endpoint security software that’s always there logging every single possible thing but I can’t do much about it. I expect the ssd to die first in this laptop at this rate, so best I can do is ensure everything always synced/backed up from my local work laptop.
Then you probably want something that has replaceable parts and not an apple product (e.g. framework)?
Not trying to discourage you from building your thing, but just figure that's worth considering.
Also, I could see why developers would want excessive logging in their betas, so that's kind of a catch-22 (without the verbose logs it might be harder to fix bugs found in the beta)
I would consider such laptops not fit for purpose and wouldn't buy one in the first place. Of course, that doesn't help if that's the sort you have. Sorry.
Regardless, if you're concerned about the logging of beta software prematurely wearing out your SSD, then don't use beta software. It's not ready for release anyway, by definition. It's there so you can help test it for the developers. Logging is an important part of that.
Last time I looked at Laptops that supported ECC it was a very short and very expensive list. At least I could get enterprise datacenter SSDs... once upon a time...
I know that I DONT want iLO/IPMI/Redfish on a laptop though, the out of band stuff eats up a ton of power.
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 :)
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.
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.
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?
> 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.)
On my personal computers I keep track of this and ensure nothing goes write-crazy.
On my work laptop though (M3 Pro, 1TB), I’m at ~70% health. Iirc the lifetime writes are at >700TB. I do develop on it, but a lot of it is due to the various endpoint security software that’s always there logging every single possible thing but I can’t do much about it. I expect the ssd to die first in this laptop at this rate, so best I can do is ensure everything always synced/backed up from my local work laptop.
What about people who want their laptop to last 10 years?
Then you probably want something that has replaceable parts and not an apple product (e.g. framework)?
Not trying to discourage you from building your thing, but just figure that's worth considering.
Also, I could see why developers would want excessive logging in their betas, so that's kind of a catch-22 (without the verbose logs it might be harder to fix bugs found in the beta)
For Macs, treat a renewable AppleCare subscription as part of the cost.
You can replace your SSD without replacing your laptop.
On some laptops, it requires a complete motherboard replacement.
Really??
I would consider such laptops not fit for purpose and wouldn't buy one in the first place. Of course, that doesn't help if that's the sort you have. Sorry.
It helps reduce size and weight since you can just directly place ssd chips on the motherboard instead of planning for connectors.
Just depends on what your priorities are.
imagine the 2 grams you'll be losing by skipping the m.2 connector
Connectors are points of failure. The less of them, the more reliable.
MacBooks are like that.
Well, then I wouldn't buy a MacBook.
Regardless, if you're concerned about the logging of beta software prematurely wearing out your SSD, then don't use beta software. It's not ready for release anyway, by definition. It's there so you can help test it for the developers. Logging is an important part of that.
I have a feeling you missed a giant "/s".
Or maybe not, can't be sure nowadays.
I think people have forgotten what year it is and how ubiquitous SoC and unified memory designs have become.
Well if 4 years decrease SSD life by 6%, then 10 years should decrease it by ~15% - so you have plenty of wiggling space.
Then you probably want enterprise level drives, motherboard, ECC RAM, etc.
I know I do!
Last time I looked at Laptops that supported ECC it was a very short and very expensive list. At least I could get enterprise datacenter SSDs... once upon a time...
I know that I DONT want iLO/IPMI/Redfish on a laptop though, the out of band stuff eats up a ton of power.
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 :)
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.
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.
> 0.3 DPWD
What does this mean?
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?
[flagged]
Please don't act like a jerk on HN. There are articles and comments criticizing Apple all the time and it's fine.