Open xurei opened 1 month ago
I agree solution 1 sounds like the better one.
Made a fix for it in main branch, let me know if this works as expected for you
There is an improvement, but there is still something incorrect :
Virtually-nothing
number 1 is incorrectly calculated
Interestingly, the order of the filters is:
But if I reorder like that:
The calculation looks correct:
What kind of filter are you using for CPU-intensive?
This is a plugin I made myself with face tracking done on the CPU. That was the most CPU intensive filter I had at hand, but you can see the same pattern with e.g. Composite Blur and these settings:
Blur algo: Box
Blur type: Area
Blur Radius: max
Passes: max
Bg source for compositing: None
Effect Mask: None
Less spectacular, but well present.
I was not able to replicate it yet:
You need a disabled filter between "Composite Blur" and "Color Correction 2"
I saw the comment just after I created 0.0.6. I was able to replicate it now and made a fix on main branch
Consider this setup: A simple scene with a source and two Effect filters:
The Profiler looks like this:
It gets even worse when you stack more filters:
This gives the wrong impression that all filters takes a lot of CPU, where only the first one is actually CPU-intensive. The source has a very high CPU usage, but the scene itself uses less CPU time, which does not make sense.
I see two options to fix this:
I think solution 1 is better: it is less confusing than solution 2 and is consistent with how sources are displayed in a scene, i. e. by showing the "Self CPU usage" of each child item, and adding them as the total CPU time of the parent element.