Workspace Rendering Times

I think that above each component there should be a little yellow box that says how many seconds it takes to render it. This would be very useful for optimization, and finding out which parts of your filter aren't very optimized.

There would obviously be an option to turn these off, or have them only appear on hover, or something, that's FF's choice. But the main thing.



(Click this for full size)

We suggested that back in the beta days, seems like if I recall Vlad basically said to RTFW (W = wiki) or something along those lines, if you wanted to learn to make more efficient rendering filters haha Plus, the render time at each component isn't always the same-for-the-same-component, it can depend on other factors like what's plugged into it, and how many blur/noise components are chained behind it etc. So there's some cpu wasted there just calculating your wasted render time if you want a read out of it on the screen. Plus for each change then, it has to recalculate those times, wasting more time, granted not much time, maybe 1 or 2 seconds or something but it just slows things back down and is kind of counter-productive really.

jffe

you know, i still think this is a good idea. but you dont base it on the component; you base it on how long that component preview/thumb image took to render. you could even do it as a component where you simply inserted the 'Time' component into your algorithm anywhere you wanted and it would simply return a value. it would be a good way to debug a slow filter or speed up an average one.

I think it sound a good idea

Better filters mean less Low Usage Filters, More High Usages, and overall good appeal in the face of Filter Forge!

It seems you have! At first it was different than mine, samples and whatnot, but at the very end Craig posted something about seconds, and that I agree would be the same here.

The overall idea about speed reports about your components is a good one. I think Vlad should get in here and talk to us about it.

Vlad, how about providing a separate compile that provides the render troubleshooting & analysis functionality we talked about here and in the other thread linked above?

This way, the average user would not have his renders slowed down by the additional 'analytical code', but a filter developer could - if necessary - launch the "troubleshooting" executable to get under the hood...

I like Dilla's idea.

Maybe not a separate exe though, like Kraellin is saying.

Quote
Vladimir Golovin wrote: I'm watching but I'm not willing to talk at this point

And what point would you be thinking about joining?

Oh I see. I wouldn't be too opposed to having a separate exe anyway. A bit of an inconvenience, yes. But nothing too bad.

I can only wait...

In February 2012 I have posted about this 2008 thread fr om Betis, but it was not the moment for Vladimir to talk about this

Now one year after, in February 2013 is already making the FF 4.0 and I want to bring back this topic that Betis started as I think it would be really helpful and useful to optimize and build the filters in a better way and get faster render results KNOWING wh ere there could be some time rendering problems between the filter components and links.

This could perhaps help much to solve possible problems like the one Morgantao found in this thread --> FF math: 30+1=163

I have seen that the same as it happens here, it can happen also with others combinations of filters that are good separate and when joined in one filter, the render time is much higher than the sum of the two