Exlude Objects: CPU heavy to parse

[nefelim4ag]

@mykepredko

Is that correct?

@mykepredko

If it is, then I think it’s a valid approach. The only comment I would make is to remove the custom KlipperScreen from the system, see if you still have what you’re describing as “hot spots”. If you do then look at the code there and see what kind of improvements can be made.

Those profiles are from vanilla Klipper.
One of them, from my RPI5, where it still takes around 1s.
I do not have fancy stuff, and generally think that RPI5 is OP.

So, I suspect those hotspots should be valid for all systems.
But I’m not sure that they will generate TTC.
The only possible difference is the amount and complexity of exclude_objects_definition per build plate.

@mykepredko

I’m only suggesting to run without KlipperScreen (of any flavour) because in the cases where I’ve helped people through TTC errors

Just my 2 cents.
I generally think that CPU can be loaded to 100% and klipper should work
Maybe with a little amount of magic dust.

I suspect that KlipperScreen is somewhat the same as the WebUI in the sense that it uses Moonraker and receives status/state updates.
So, if there is large JSON data (512kb, as in the above screenshot) (high amount of excluded object definitions), that large JSON serialized and deserialized should consume the power of Klipper, then Moonraker, and then Klipper screen.