Earlier quoted context omitted.
Nice find. I always have seconds displayed, but disabling it reduced the CPU load to 0%
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…
Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
71–80 of 145 posts
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#72Earlier quoted context omitted.
> 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 occu…
"let's say for the sake of argument" is doing a fair bit of work here. But the point is that we had text editors (similar to the ones we have today) back when CPUs were capable of maybe a few millions of instructions per second. CPUs can now do tens or hundreds of thousands as many instructions, but a text editor today uses several percent of that CPU. That would be like shipping a square kilometer of forest to the j…
Whether or not those efficiencies are achieved is left as an exercice to the reader.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#73Turning off "Display the time with seconds" lowers the 1% CPU load to 0% for me.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#74Turning off "Display the time with seconds" lowers the 1% CPU load to 0% for me.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#75Earlier quoted context omitted.
To be fair, 8gb hasn't been quite enough for most dev work since containers and VMs became a standard way for local builds and runs.
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.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#76I 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…
How many of these problems can be overcome by simply running the tools in the browser and not as standalone apps?
However, for real desktop tools that utilize the operating system's bells and whistles, which truly make an app a desktop app—like Sublime—I'd never use an alternative in the browser.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#77I 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…
How many of these problems can be overcome by simply running the tools in the browser and not as standalone apps?
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#78Earlier 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.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#79Earlier quoted context omitted.
Nice find. I always have seconds displayed, but disabling it reduced the CPU load to 0%
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…
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#80I 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…
How many of these problems can be overcome by simply running the tools in the browser and not as standalone apps?
Arc seems somewhat resistant to large memory grab issues, but the Notion database kills it as well.