i have plenty of GOPs in my main script. should i pause some subpatches somehow? like some that are not in use but have objects. what are your go-to methods for conserving cpu?
-
cpu saving methods - should i pause subpatches that are just leftovers and not in use?
-
@esaruoho The [switch~] object allows you to toggle the dsp of subpatches and abstractions, just put it in a subpatch or abstraction and send it a one or a zero to enable or disable its DSP..
-
Actually the process that is 70% CPU is the GUI process, the lowercase letter one is the one doing the audio
That 70% is probably just from drawing a lot of GUI stuff -
@seb-harmonik.ar said:
Actually the process that is 70% CPU is the GUI process, the lowercase letter one is the one doing the audio
That 70% is probably just from drawing a lot of GUI stuffthat's very interesting! so it seems like my best choice would be to start looking at optimizing the amount of GOP stuff i have, as my GUI for the main script is pretty busy.
ok looks like just simply dumping the
[else/spectrograph~]
(the large pink one), resulted in a massive drop
EDIT: just noticed one interesting thing. whichever part of the script i'm in (lower part or top part), has a massive effect on CPU usage. it's the one with more GOPs (the mixer strips) that ramps Pd up to 80% or more. so now i gotta figure out how to start reducing the GUI load.
-
ok THIS was good. so i removed 16 instances of
[else/detect~ hz]
and their[else/numbox~]
and immediately experienced a jump from 85% CPU on Pd to 23%-35%..
i also realized i didn't really need that info anyway so.. i've lost nothing and gained a lot of cpu cycles.