Not sure what to call this... Filter Diagnostics?

It's been requested a couple times in the past. I feel that "fast / slow" thing is kinda neat if we could have some counters on each node to see what's really bogging stuff down. Some numbers would encourage people to consider alternative node noodling to get some filters optimized.

At the same time, I feel some things are a bit more subjective. In Substance Designer, you can do exactly what you're saying. You can display little timers on each node to see bottlenecks. This is partly because Substance does have a real-time application and it makes sense to have that kind of display. FilterForge doesn't have the sort of necessity to do that. Generally, people here would rather get the filter to look like their desired output than to construct a highly efficient procedural effect. At least that's how I see it.

As of now, we have the elapsed time of render display. That can be helpful in assessing slow filters. And there's a simple, general list of "fast components" vs "slow components" that's mildly out of date right now that we have. With experience, it's easy to see where the bottlenecks usually are... I always have some suspect within my filters.

Either way, I think diagnostics would be a good idea. It's better to have more data than it being abstracted!