SetupRenderersForCamera can be slow

[JonnyOThan]

It looks like this is doing some kind of custom renderqueue sorting. With the other optimizations going on, this is now taking 10-12% of the LateUpdate time.

I haven't dug in yet so I don't have any great ideas about what to do, but maybe:

• can we do this only if we detect something changed about the camera?
• are there materials in this list that don't need to be?
• How many of the renderers are disabled, and are we paying significant overhead to check that? Sorting them by enabled status (and then having some way to update the order) might help

[JonnyOThan]

Some stats: Using SWE, a single poodle has 57 renderers.

When it's not active, 3 go through the distort path and 21 through the bounds path - so only 24 of the renderers are active.

When it's active, there are still 3 in distort and 36 in bounds. Only 39 renderers are active??

Here's one of the disabled renderers - is this for a different variant maybe?

liquidEngine2-2.v2/model/StockWaterfallEffects/Engine Configurations/poodle_plumes(Clone)/DoubleBell/Gimbal/doublePlume/Waterfall_FX_exitTracesLong_1/Waterfall/FX/fx-cylinder(Clone)/Cylinder

I think not - I was using the double plume variant, but not quite sure what's going on here.