macOS CPU performance related to WindowServer
Re: macOS CPU performance related to WindowServer
No laggy visuals, no laggy anything. Live looks exactly the same and behaves exactly the same.
Except Live’s cpu usage drops like a stone. On my Mac from 30+% for a new project with no audio, plugins or MIDI in it and audio dropouts once the meter hits 35% to 5-6% and still stable at 70%+..
Except Live’s cpu usage drops like a stone. On my Mac from 30+% for a new project with no audio, plugins or MIDI in it and audio dropouts once the meter hits 35% to 5-6% and still stable at 70%+..
Live 10 Suite, 2020 27" iMac, 3.6 GHz i9, MacOS Catalina, RME UFX, assorted synths, guitars and stuff.
Re: macOS CPU performance related to WindowServer
Unfortunally this does not seem to work for me. I have tried every single advice i could find, including Options.txt, but still experience laggy behaviour, GPU spikes on AMD Radeon Pro, and fans that are runing like crazy. The only thing that works is to hide the Ableton window.... but that is kind of i impracticable.... I use a 16 inch Macbook pro 2019 with Catalina. Anyone else have the same problem?
-
- Posts: 4478
- Joined: Wed Oct 24, 2007 4:50 am
Re: macOS CPU performance related to WindowServer
are you using an external display?zangpa wrote: ↑Sun Feb 16, 2020 1:39 pmUnfortunally this does not seem to work for me. I have tried every single advice i could find, including Options.txt, but still experience laggy behaviour, GPU spikes on AMD Radeon Pro, and fans that are runing like crazy. The only thing that works is to hide the Ableton window.... but that is kind of i impracticable.... I use a 16 inch Macbook pro 2019 with Catalina. Anyone else have the same problem?
Re: macOS CPU performance related to WindowServer
Have you tried preventing GPU switching? I remember seeing something about this on Apple’s user forum or help web site but can’t find the link to it, sorry.
Live 10 Suite, 2020 27" iMac, 3.6 GHz i9, MacOS Catalina, RME UFX, assorted synths, guitars and stuff.
Re: macOS CPU performance related to WindowServer
I did this to the extreme settings "15" and I noticed ableton became laggy... but I also think my CPU % improved a little....
Is this what it does, make the frame slower? and make the graphics more laggy? How does that improve the CPU?
Is this what it does, make the frame slower? and make the graphics more laggy? How does that improve the CPU?
Re: macOS CPU performance related to WindowServer
It basically drops Live’s screen refresh rate. “15” is probably going to be a bit laggy, but I can’t tell the difference in terms of graphics response between 30 and not making the options.txt change.
It made a huge difference to my 2014/15 Retina i7 MBP, which has Intel graphics, and makes hardly any difference at all to my new 2020 27” i9 iMac, which as well as a much faster cpu (and more RAM) has a dedicated video card. The MBP was basically unusable with Live 10 without dropping the refresh rate - an empty default standard project template with the transport not running sent Live’s resource meter to 35%+ and dropouts started when Live’s meter hit around 40%. The options.txt trick dropped Live’s resource meter to 4 or 5% when idle and crackling didn’t start until around 75%.
The WindowServer is a core part of a Mac’s OS, it’s what applications and the OS uses to draw stuff on the display. Things which constantly update tend to use it a lot, and it uses cpu cycles to do its stuff so lots of screen updating can and will increase cpu load.
Another thing which might help reduce graphics load based cpu usage is to use the “reduce transparency” option in the Accessibility part of Settings.
It made a huge difference to my 2014/15 Retina i7 MBP, which has Intel graphics, and makes hardly any difference at all to my new 2020 27” i9 iMac, which as well as a much faster cpu (and more RAM) has a dedicated video card. The MBP was basically unusable with Live 10 without dropping the refresh rate - an empty default standard project template with the transport not running sent Live’s resource meter to 35%+ and dropouts started when Live’s meter hit around 40%. The options.txt trick dropped Live’s resource meter to 4 or 5% when idle and crackling didn’t start until around 75%.
The WindowServer is a core part of a Mac’s OS, it’s what applications and the OS uses to draw stuff on the display. Things which constantly update tend to use it a lot, and it uses cpu cycles to do its stuff so lots of screen updating can and will increase cpu load.
Another thing which might help reduce graphics load based cpu usage is to use the “reduce transparency” option in the Accessibility part of Settings.
Live 10 Suite, 2020 27" iMac, 3.6 GHz i9, MacOS Catalina, RME UFX, assorted synths, guitars and stuff.
Re: macOS CPU performance related to WindowServer
As far as I can see this is not available anymore in Live 11, correct?
Mac Studio M2 Max and MacBook Pro M1
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Re: macOS CPU performance related to WindowServer
I'd love to know this as wellAs far as I can see this is not available anymore in Live 11, correct?
Re: macOS CPU performance related to WindowServer
I'm getting this same error. Any solutions?
Re: macOS CPU performance related to WindowServer
It's still here but the option name's changed. I can't remember it, I probably have the info somewhere around my hard drive, I need to check.
You could also ask to support@ableton.com if I'm not coming back with the answer quickly enough.
You could also ask to support@ableton.com if I'm not coming back with the answer quickly enough.
Ableton Forum Moderator
-
- Posts: 2
- Joined: Wed Dec 01, 2021 7:20 am
Re: macOS CPU performance related to WindowServer
Hey! Just found the line today on reddit for Live 11.
Here you go:
"-MaxUiFrameRateHz=30"
or any number you want instead of "30".
Cheers!
Here you go:
"-MaxUiFrameRateHz=30"
or any number you want instead of "30".
Cheers!