Live data from Hacker News

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

twitter.com

41–50 of 145 posts

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

#42
post #18

Earlier quoted context omitted.

Meanwhile Apple is the company most actively working on better battery performance, less memory utilization (e.g. compressed memory) and other such changes...

> compressed memory doesn't solve much and it's been available in all other OS for a long time. many reported that compressed memory can negatively impact performances in certain scenarios For example https://github.com/microsoft/Windows-Dev-Performance/issues/...

Don't know how compressed memory works for in Windows, but on macOS its role is equivalent to swapping. No memory is compressed unless pages are evicted due to not being used. If memory compression wasn't present then it'd been swapped to disk.

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

#44
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.

Best way to use Electron stuff, is via the Web app.

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

#45
post #35

Earlier quoted context omitted.

Because Teams, and also because Electron.

That’s essentially a circular argument. “Teams is bad because it’s slow. It’s slow because it’s Teams.”

As a Teams user on the crappy PCs the company gives, this is an argument I can get behind.

It looks circular but there are implicit meanings hidden there:

"Teams is bad (not only) because it’s slow. It’s slow because it’s Teams. (as in, Teams has a looong list of defects, slowness just icing on the cake)”

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

#46
post #4

Is FB13204831 the bug ticket? https://nitter.net/tomaskafka/status/1706403105661722849#m

It's the Apple feedback thing. https://developer.apple.com/bug-reporting/ They're not public of course, because it's an apple thing.

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

#47
post #18
post #3

Earlier quoted context omitted.

The fix will be ready for the next macOS Apple Event so that they can claim battery performance improvements

Meanwhile Apple is the company most actively working on better battery performance, less memory utilization (e.g. compressed memory) and other such changes...

MacOS had compressed memory for at least a decade

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

#48

https://tonsky.me/blog/disenchantment/

> Modern cars work, let’s say for the sake of argument, at 98% of what’s physically possible with the current engine design. Modern buildings use just enough material to fulfill their function and stay safe under the given conditions. All planes converged to the optimal size/form/load and basically look the same.

Is this all true? I'm somewhat sceptical of extrapolating that broken processes and waste don't also occur in other industries. A quick Google search says around 30% of building materials delivered to building sites is wasted. I've also seen some pretty impractically designed buildings in my city that probably waste a lot more energy and people's time than they should.

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

#49
post #35

Earlier quoted context omitted.

That’s essentially a circular argument. “Teams is bad because it’s slow. It’s slow because it’s Teams.”

As a Teams user on the crappy PCs the company gives, this is an argument I can get behind. It looks circular but there are implicit meanings hidden there: "Teams is bad (not only) because it’s slow. It’s slow because it’s Teams. (as in, Teams has a looong list of defects, slowness just icing on the cake)”

Yeah fair.

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

#50
post #39

That's probably a good amount of battery life that can be claimed back once this is fixed

Fixed ? This is modern UX design.(drawing the whole screen when the cursor blinks)

It's not a UX issue whether to redraw a larger area than where the changes are.
Post reply on HN