my 2017 i7 15" MBP on Catalina - it's at 1.26PB and 121% but seems to be working fine:
my 3 week old M1 Mac Mini 16GB/512:
my 3 week old M1 Mac Mini 16GB/512:
Anybody knows what this means in WD Blue SSD's SMART:
Does the SSD have both SLC & TLC? Internal fusion ssd?Code:233 NAND_GB_Written_TLC 0x0032 100 100 --- Old_age Always - 62056 234 NAND_GB_Written_SLC 0x0032 100 100 --- Old_age Always - 67017
Let's just shut the message board down. Will that be acceptable to you? (Hint: you could just ignore the thread, like I ignore threads that don't interest me).I am saying that the people freaking out and losing their mind are doing so over speculation that their devices are suddenly going to blow up or become useless in the next year, just read through this thread and its 80% of the posts.
Since these systems are not walled garden iOS devices the ability to run anything the user wants makes me more suspicious that people reporting hundreds of TB written might be running some weird applications that they don't fully understand. If everyone was seeing that figure it would be a very different story, but those users are few and so far I have seen no data on what they run on those systems. I am by no means saying Apple couldn't have screwed up, they have done it plenty of times. I've just seen this forum blow up over the dumbest rumors, it's happening again in this thread. People should just report the issue to Apple and wait for a reply, rather we have almost 20 pages of discussion on a couple of tweets.
I considered this when I first started seeing excessive kernel activity / disk writing. In discussion with Apple Support I erased the disk, did a clean install of Big Sur and manually and gradually rebuilt my profile. I used the M1, logged in via iCloud, but not initially adding any third-party apps and the excessive kernel activity was present. With the first migration-based install, I was seeing lots of beach balling after a few hours of uptime. After the clean install, I have no performance issues (even after adding back in all of my regular apps).I agree that people sometimes do stupid things with their machines, but some people over at Hacker News are also experiencing the issue, and that's a pretty competent crowd.
1.25 PB!my 2017 i7 15" MBP on Catalina - it's at 1.26PB and 121% but seems to be working fine:
View attachment 1734574
my 3 week old M1 Mac Mini 16GB/512:
View attachment 1734575
Let's just shut the message board down. Will that be acceptable to you? (Hint: you could just ignore the thread, like I ignore threads that don't interest me).
My 2011 Mac mini running 10.13 (and Windows 10) says hello. My husbands 2009 white MacBook running 10.13 also says hello.
Security vulnerabilities say hello to High Sierra without security updates.
Who on this thread is "freaking out". A lot of people expressing concern. I was going to jump on a refurb today but will hold off until this is resolved.It's odd you think this isn't of interest to me. Me not freaking out about it doesn't mean I am not interested in a topic.
*raises hand*Oh man this thread is still kicking. You guys get some serious hype about a lot of speculation. How many of you have submitted a bug report to Apple over this?
Who on this thread is "freaking out". A lot of people expressing concern. I was going to jump on a refurb today but will hold off until this is resolved.
It is not a question of RAM. MacOS is written by idiots. Most of what otherwise would be free memory is occupied by cached files (check your activity monitor). Instead of reducing the cached amount when the memory pressure increases and when the compressed ram can't hold more, RAM content is swapped on the SSD. MacOS also writes excessively (on my machine with Firefox set to minimum writes) - at least 10GB per day. My Linux box with the same amount of RAM (16GB) writes less than 200MB daily. The SSD life is simple to calculate. TLC can sustain ~1000 writes per cell. So you take the free space on your SSD multiply by 1000 and divide by the daily usage. If 128GB are free on a SSD of any size, if MacOS writes 20GB per day, we have 128*1000/20=6400 days or 17 years. If you write twice that amount each day, the life will be halved to a little more than 8 years. And I've personally seen 100GB writes per day!!!Isn't this exactly what was predicted with inadequate RAM they put in stock models?
I would be very concerned, if there is a true issue, about soldered SSDs and the resale of my product. There is another thread, with some very bright people (way smarter than me) posting in it, who are concerned about the inexplicable SSD usage and the impact on the life expectancy of the SSD.Oh it's the usual complaints:
Apple screwing us because they engineered a bad product; Apple screwed us by putting soldered SSDs when the device is going to die in a year; This is why you never buy first generation products; "I should have not bought this product, the resale is plummeting!"
It's the usual tripe spewed here. You're welcome to review the past 20 pages if you actually want to find out.
It is not a bug! MacOS has always been excessive on writes with launchd and kernel_task being the worst offenders. No other operating system behaves this way. And YES, I also have Linux and Windows computers.So is this SSD excessive wear a Mac OS bug or hardware issue? I'm still in the return period on my MBA M1 8/16/512. I'm not sure if I should return it and get a good Windows laptop or to purchase AppleCare for my MBA. What is your recommendation?
I would be very concerned, if there is a true issue, about soldered SSDs and the resale of my product. There is another thread, with some very bright people (way smarter than me) posting in it, who are concerned about the inexplicable SSD usage and the impact on the life expectancy of the SSD.
While people may use hyperbole, the hyperbole is no better or worse than the hyperbole I see from the same people over and over defending Apple on almost every thread (not directed at you).
Personally, I'm concerned enough to see how this shakes out before I buy (I was literally ready to buy one of the refurbs that came out last night) and to see if 8gig of ram has any influence vs 16. I don't want to be in a position of buying something that becomes essentially worthless in two years (if that is the case)....right now....I just am not confident either way.
Unlike the current Apple offerings, your 2012 laptops are all using replaceable SSD-s, so this is not an issue.Just for the sake of assuaging some of worry: I've got quite a few 4GB and 8GB MacBook Airs and 8GB MacBook Pros w/Retina from as far back as 2012 with the built-in Apple solid-state storage in education deployment. The Airs only have 120GB of storage. Zero of these have experience any storage-related failures to date. The "Disk Drill SSD Health Level" on an 8GB 2012 MacBook Pro Retina with 250GB SSD reports at "96% for whatever that's worth, on a machine that's been hammered on pretty hard every school-day for 8 years. I realize that's not the same test being run in this thread, but I'm not going to bother installing homebrew to do this. Unless something has gone catastrophically wrong with BigSur (which, let's be honest, is certainly possible), then we *probably* don't have anything major to worry about. If something has gone wrong and BigSur really is writing massive amounts of data as reported, then *probably* Apple will fix it, because they really don't want the class-action lawsuits and horrible press they will get when their OS causes their computers to die in just a handful of years. Either way, it's going to take a lot of failures on Apple's part for this to impact end-users. Apple would have to be the kind of company that designs, builds and sells an utterly failed industry-worst keyboard for 5 years straight to let something like this get away from them, and they couldn't be that kind of company, could they? (Wait, I didn't do a very good job of assuaging worry, did I? But really, unlike the keyboard travesty, I do expect this will turn out to be either a temporary glitch or a non-issue.)
I checked and some late 2009 iMac can take up to 10.13.6. I didn’t check any other models listed. I know that my 2010 iMac is supported, mostly because I don’t care much for High Sierra myself but prefer the last supported release on any older hardware I own.Okay, I remebered the year wrong, I'll correct my post after hooverin in Mactracker.
Right year would be pre 2010?
I've wondered about the use of Swap since considering buying a new Mac that has soldered SSD. I don't quite understand fully how RAM works, but I feel like I have a general understanding of it. That said, I can't understand how this scenario works out. I just restarted my computer (New M1 MBP) only opened Safari, this particular thread- went to the last page, logged in, and took this screenshot. How is it that 2 pages of this thread needs 500+ MB written into memory? I'm not saying there is an issue- but would love if anyone could clarify what is going on behind the scenes. I'm familiar with generally what a typical file size would be for misc filetypes, and I can't comprehend why these two pages would equal that much. What am I missing?
Thanks for any insight!