Filter Timing

Please add some sort of performance evaluation functionality to filter forge.

This request is motivated by the two following challenges:
1. being able to identify performance of library filters (I'm not interested in dead slow filters)
2. being able to optimize/construct more optimal filters

Some ideas for a solution:
- Profile the sample time of components inside filters and add it all up
- Do some basic internal rating of components. Count the number of sample draws (it would be very useful if I could see the bomber/whatever component being queried 18 times output sample or so)
- Time a known complex build in filter (preferably something that uses a lot of different components), compare any other filter performance to that reference and use it to put together some absolute performance rating that anyone can relate to.

+2
I would totally support the filter timing - it would also help to figure out, which components are slowing down your filter (for those who don't know yet that blurs, highpass, etc. are expensive)

One idea I am having here: You can enable 'analyze-mode' which will highlight the nodes in your filter that use most cycles. (see the mockup that explains it)

Or do it like the <ahem> substance guys </ahem> who print the timing under each node. I guess that's not something that they have patented. I am often surprised how many noises I can stack, but then one single blur takes away all my performance. Knowing about timings is crucial for ambitious filter designers.

I'm in complete agreement about this as well. Any node based program like this will always benefit from node level timing like Substance has. It would benefit users for more than just debugging purposes too. In general having this readily displayed for each node would eventually help in the way people construct nodes from the very beginning. They would unconsciously be thinking of these timers and how to build the node graph more efficiently after enough time and exposure to them.