Consider this setup:
A simple scene with a source and two Effect filters:
the first one is highly CPU intensive
the second one is virtually nothing (i.e. a Color Correction filter with defaults parameters)
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:
show the CPU usage of the filters MINUS the CPU usage of the filters above it,
- or -
only add the CPU usage of the last filter to the CPU usage of the source, and maybe show the filters in a waterfall view (but this might quickly become unreadable for sources with many filters)
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.
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.