Re: OSX Push2DisplayProcess CPU usage
Posted: Thu Feb 08, 2018 9:33 pm
From what I can gather this issue of unexpected high usage is another Mac specific issue and related to slightly older hardware?
I did a few (unscientific) tests between the same project on L9 and L10 and noticed absolutely zero difference in the display process. The track I was using would use approx 45% of CPU cycles (as reported by task monitor, not Live), 9.5GB of RAM and Push only peaked at 8% usage no matter what display mode I was in (including the graphic display of EQ8)
Certainly might be something they have to look into if info can be sent as to the setups. I have to agree tho, a dual core is not going to be very efficient. Not that Push requires it but overall it doesn't have many cores to divide the work over... I haven't used a dual core since about 2011.
I did a few (unscientific) tests between the same project on L9 and L10 and noticed absolutely zero difference in the display process. The track I was using would use approx 45% of CPU cycles (as reported by task monitor, not Live), 9.5GB of RAM and Push only peaked at 8% usage no matter what display mode I was in (including the graphic display of EQ8)
Certainly might be something they have to look into if info can be sent as to the setups. I have to agree tho, a dual core is not going to be very efficient. Not that Push requires it but overall it doesn't have many cores to divide the work over... I haven't used a dual core since about 2011.