It can be hundreds of RAW images (50MB/image) or the simulation software I'm working on which can generate GBs of output in 3 seconds if I leave the wrong flags on.
In my other workstation I can actually see the big jumps of write accumulation when I do these tasks via SMART (I log the data periodically).
So mine was a honest question rather than covert fanboyism.
If you were spending more to get better endurance, you could have just bought the 2TB version, which would have guaranteed 1422 GB/day.
(NB: SSDs suffer write amplification, so if you actually need 1.4TB of writes per day you should choose an enterprise drive instead.)
Endurance isn't a problem with SSDs for consumers, at all. Even QLC, which has significantly worse endurance than TLC, has plenty.
I have a slower storage tier on that computer for big files and archives so, it's only hammered when I really need that speed.
When I bought the Mac, 1TB SSD was top of the line. 2TB was not available for Mid 2014 Macs. Actually, I upgraded everything as apple could while buying it
I'm aware of the dynamics of SSD writes and TBW values. I personally don't write that brutally. Things get hot if I'm processing images or working on my software and need to see some detailed logs or interim results along the way.
If I was using my computer as an ordinary user, I'd not worry about it at all. My family's computer runs on much simpler drives and their write volume is nowhere near me.
This is why I paid or a 1TB SSD on the Mac. I guessed that I'd wear it down faster but nope, that thing holds.
Periodically I graph the data with GNUPlot. There's a slight slope most of the time. In some regions there are jumps. These are generally when I seriously work with my software, generating logs and other output.
System is on another SSD and swap is on a high performance HDD so, they do not affect the graphs I'm getting.
That jumps helped me to catch two KDE bugs. One was an isolated case with akonadi. Other one was reported and possibly KRunner's bookmarks extension will see some more revisions to eliminate disk trashing.
Addendum: When I have spare time, I'd write a small HTML/JS file to get the data from log file and graph it interactively. A both fun and useful project.
