3 ms·

My experience exactly mirrors yours. Battery life is really good. Processing speed is good, but it's not like stuff compiles instantly now. There are, contradic

My experience exactly mirrors yours. Battery life is really good. Processing speed is good, but it's not like stuff compiles instantly now. There are, contradicting reviews, waiting times. I've seen many beach balls using my MBP and it comes free with a couple of issues: - After a few hours of developing an Angular app using ng serve kernel_task consumes insane amounts of CPU time, resulting in extreme lag and completely locking up the device on an attempted restart (not even the touchpad clicks anymore). - Sometimes MPEG4 videos just would not play until after a reboot That said: Besides some minor UI glitches it's really, really solid. x86 compatibility is perfect. The GPU is good (again, not amazing, but Minecraft runs at good settings). Over all it's not revolutionary. Slow software is going to be slow on these too. What they pulled off is amazing ecosystem wise, but as an end user you can be happy about some non-revolutionary pretty good decent spec bumps. I just worry about the SSD's life. I'm already about 20TB down after a few weeks.

joshstrange 5y ago
The SSD issue appears to have just been a reporting issue and it was fixed in 11.4: https://appleinsider.com/articles/21/06/04/apple-resolves-m1-mac-ssd-storage-longevity-issue-in-macos-114-beta https://appleinsider.com/articles/21/06/04/apple-resolves-m1...
- solarkraft 5y ago
  I'm on the 12.0 beta, though. The article also doesn't put any hard numbers on the actual expectancy. If the smartmontools reading is wrong, what's my estimated actual TBW? Because at that speed it won't take all that long to reach the rated amount for a typical SSD (even at a multi X factor we'd still be talking about a low number of years).
iaml 5y ago
> kernel_task consumes insane amounts of CPU time If my understanding of how mac works is correct, this is caused by overheating and basically is throttle mode.
- soneil 5y ago
  That's my understanding. It's how the OS accounts for the overhead that's unavailable. So if kernel_task is using 20% leaving 80% for userland, what's actually happening is your cpu is throttled to 80%. It's also why it's the go-to to blame for performance issues - it's the symptom not the cause. Your laptop isn't running warm because kernel_task is at 80% - but vice versa. Over 8 cores this figure can start to look crazy. (eg 80% kernel_task can be 8 cores * 10%)
- solarkraft 5y ago
  That's the main source of high kernel_task CPU usage on Intel macs, but M1s don't really get that warm, especially not with active cooling like my device has. So that's probably not it, though a glitching temp sensor might be at fault. What tends to speak against it is that the issue seems to mostly, but not fully, disappear once I stop ng serve (running on nodejs v16.4.0).

joshstrange 5y ago

The SSD issue appears to have just been a reporting issue and it was fixed in 11.4: https://appleinsider.com/articles/21/06/04/apple-resolves-m1-mac-ssd-storage-longevity-issue-in-macos-114-beta https://appleinsider.com/articles/21/06/04/apple-resolves-m1...

solarkraft 5y ago
I'm on the 12.0 beta, though. The article also doesn't put any hard numbers on the actual expectancy. If the smartmontools reading is wrong, what's my estimated actual TBW? Because at that speed it won't take all that long to reach the rated amount for a typical SSD (even at a multi X factor we'd still be talking about a low number of years).

iaml 5y ago

> kernel_task consumes insane amounts of CPU time If my understanding of how mac works is correct, this is caused by overheating and basically is throttle mode.

soneil 5y ago
That's my understanding. It's how the OS accounts for the overhead that's unavailable. So if kernel_task is using 20% leaving 80% for userland, what's actually happening is your cpu is throttled to 80%. It's also why it's the go-to to blame for performance issues - it's the symptom not the cause. Your laptop isn't running warm because kernel_task is at 80% - but vice versa. Over 8 cores this figure can start to look crazy. (eg 80% kernel_task can be 8 cores * 10%)
solarkraft 5y ago
That's the main source of high kernel_task CPU usage on Intel macs, but M1s don't really get that warm, especially not with active cooling like my device has. So that's probably not it, though a glitching temp sensor might be at fault. What tends to speak against it is that the issue seems to mostly, but not fully, disappear once I stop ng serve (running on nodejs v16.4.0).