Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

twitter.com

Post reply on HN
Print view View original

91–100 of 145 posts

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#91

Post by Aloha »

klodolph wrote: post #66
gcanyon wrote: post #56

I am currently at war with google docs and notion re: memory usage. gmail takes something like half a gigabyte of memory. I had a notion database where each time it loaded an additional 25 rows, memory use went up 400MB. It only got up to 200-300 rows total before it died. I gave up Sublime because of memory usage, but the alternatives aren't much better. I'm getting ready to trade in my 8gb Mac for 24gb to help with…

Consider BBEdit. I’ve been using it a lot more these days, now that its competition has skyrocketed in CPU / memory.

BBEdit has been my go to for a long time, as a person who came from Windows, it was a good replacement for Notepad++.

I'd love to buy it, but while I'd be happy to pay 99 bucks for a perpetual version with upgrades, I'm not willing to pay 50 dollars every unknown amount of time. Even if I might pay that for a known 5 years worth of updates.

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#92

Post by monocularvision »

wasyl wrote: post #63
alberth wrote: post #11

Off topic: I wish someone would do this kind of analysis to determine why Microsoft Teams helper process is always at 50-70% CPU load on my M-Based MacBook Pro. My laptop is warm/hot to touch as a result of it.

I wish someone did an analysis to determine why my intel-based macbook is so incredibly laggy all the time, even after fresh system installation. I can't shake the feeling that Apple Silicon is so much faster that performance issues just got into the system without anyone at Apple bothering to fix them, and Intel macs suffer as a result.

My wife’s Intel-based laptop got considerably slower in the last year or so. I tried everything I could but nothing seemed to return it to its original performance.

Then she got a warning that the battery needed servicing. After getting it replaced (and the Apple employee warning us several times that it might not help performance), the laptop was back to its previous state. My theory is that the battery running warmer was causing the CPU to throttle. Or perhaps cleaning out the machine while replacing the battery helped it thermally. Or maybe both.

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#93

Post by solarkraft »

Control center is one of the worst parts of my macOS usage. It keeps taking seconds to (abruptly) show up and on my multi-monitor system it sometimes shows up between corners or on the opposite site of the monitor I activated it on.

I wish it could be disabled and the controls put into the menu bar, but infuriatingly you can't.

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#94

Post by sgt »

wlesieutre wrote: post #75
miroljub wrote: post #62

Earlier quoted context omitted.

I don't think it's an excuse for Notion. It's not like it's spinning a new container for each and every database row.

You never know, maybe that's their row microservice.

Or the overheads for communication between the row and column services, the latter being spun up dynamically based on the column count.

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#95

Post by solarkraft »

viraptor wrote: post #40
londons_explore wrote: post #27

Earlier quoted context omitted.

It must not always be the case. I'm sure they have a power team at Apple who ensure a Mac can sit on the desktop without any CPU wake-ups.

They may have a team, but they actually need to use it. Given the amount of bigger broken things in the new MacOS version, I wouldn't hold my breath.

It's kind of crazy how broken some things like stage mangler are. It's like it has never been used once.

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#96

Post by irrational »

solarkraft wrote: post #93

Control center is one of the worst parts of my macOS usage. It keeps taking seconds to (abruptly) show up and on my multi-monitor system it sometimes shows up between corners or on the opposite site of the monitor I activated it on. I wish it could be disabled and the controls put into the menu bar, but infuriatingly you can't.

I've been using a mac for decades, but had no idea what control center was until about 1 minute ago when I read your comment and googled it. What in the world does control center provide that you find so essential?

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#97

Post by kec »

andreyv wrote: post #71
fifafu wrote: post #64

Earlier quoted context omitted.

Just be aware that 1% on modern multi-core systems is not a lot. The macOS activity monitor doesn't calculate the average percentage over all cores, instead (AFAIK) a process on e.g. a M1 Pro/Max can use up to 1000% if it utilizes all 10 cores. Stuff like this will be run on the efficiency cores, I doubt it will have a lot of impact on anything. You can see the usage of efficiency vs performance cores by using Activi…

1% is still a lot for power saving. If the system is idle, it should be at 0%. If it is anything above, then it shows poor design.

You can’t really make this claim without measuring the actual impact, especially on a system with frequency scaling and 8+ heterogenous cores.

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#98

Post by irrational »

solarkraft wrote: post #95
viraptor wrote: post #40

Earlier quoted context omitted.

They may have a team, but they actually need to use it. Given the amount of bigger broken things in the new MacOS version, I wouldn't hold my breath.

It's kind of crazy how broken some things like stage mangler are. It's like it has never been used once.

> It's like it has never been used once.

This may be the case. I worked on a website at work, but never really used the website. One day I was watching someone use it and noticed a bug. I asked the person if they had ever seen that before and they said all the time. I asked them why they didn't report it and they said that they knew we were busy and didn't want to bother us.

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#99

Post by anileated »

solarkraft wrote: post #95
viraptor wrote: post #40

Earlier quoted context omitted.

They may have a team, but they actually need to use it. Given the amount of bigger broken things in the new MacOS version, I wouldn't hold my breath.

It's kind of crazy how broken some things like stage mangler are. It's like it has never been used once.

I turned on Stage Manager around the time it was implemented in macOS, to try. I never turned it off. It has addressed pretty much every window management woe I had.

Furthermore, I am impressed how they nailed it from the first time: there were no changes since it came out that I noticed, nor would I want any.

There was a slight learning curve, you need to have a good mental model of how it works, but after a day I cannot imagine going back.

(I hate using it on iPad though.)

Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load

#100

Post by linux2647 »

droopyEyelids wrote: post #88
gcanyon wrote: post #56

I am currently at war with google docs and notion re: memory usage. gmail takes something like half a gigabyte of memory. I had a notion database where each time it loaded an additional 25 rows, memory use went up 400MB. It only got up to 200-300 rows total before it died. I gave up Sublime because of memory usage, but the alternatives aren't much better. I'm getting ready to trade in my 8gb Mac for 24gb to help with…

For the gmail issue, I feel like I might as well plug http://mimestream.com , a gmail client that is a pleasure to use & efficient.

And written using Mac APIs, not Electron
Post reply on HN