Rodrigo

So I've got a really big patch/project (over 200 files/abstractions/bpatchers/etc...) that I've been optimizing recently, and after making some really good headway on the CPU usage, I've kind of stuck on how "sluggish" the whole thing feels.

Even though I have most things wrapped in polys, and things dynamically load as needed etc.., the sheer scale of the patch (and running it at 64/64 in a performance context) was pretty rough on the CPU. Thanks to some tips and tricks from a friend (@stkr) I managed to get the idle CPU (as shown in Max) from 60-70% down to 10-15%, which I'm super pleased about!

What I'm struggling with at the moment, however, is the scheduler thread. As in, UI objects are super jumpy and jittery. This is mainly noticeable in playhead for a [karma~] object (basically a multislider that's following the 'position' outlet of [karma~]).

As far as I can tell, there's nothing really stupid going on (like [uzi]s and crazy fast [metro]s), so nothing jumps out to me what to fix. And deleting sections of the patch to test improves things, but no "smoking gun" has turned up in doing this.

Putting the scheduler in audio interrupt seems to have no impact either (and overdrive I always leave turned on).

The really bizzare thing is that the patch runs smoother in Max7 (in terms of UI sluggishness), which surprised the shit out of me as Max8 has been a dream in terms of performance, and load time.

So I've got a really big patch/project (over 200 files/abstractions/bpatchers/etc...) that I've been optimizing recently, and after making s

optimizing-the-scheduler-in-a-really-big-patch

put a bunch of [qlim 17]s before every GUI object?

Maybe checking the refresh rate of your [number~] objects, things like that, or [mousestate] if you're using it.

For all things like the playhead display you mention, you could have something like a master [qmetro 25] refreshing this kind of data.

Maybe checking the refresh rate of your [number~] objects, things like that, or [mousestate] if you're using it.
For all things like the playhead display you mention, you could have something like a master [qmetro 25] refreshing this kind of data.

I don't have any [number~] things, and I do do a bit of [mousestate] or muting [snapshots] and such when windows are closed and stuff.

I will try doing some [qlim]-ing of UI objects that refresh constantly to see if that tightens stuff up some.

yes make sure none of the UI objects are running faster than 60fps

Optimizing the scheduler? (in a really big patch)