Slow performance?

[juanjgon]

Hmm, the problem related to the freeze after aborting a render should be fixed in the Octane test4 API. Is there anything special in these scenes, like a composite background or something like that?

Thanks,
-Juanjo

[Builtdown]

I´m using Octane 3.05.
To me it seems that the l-o-n-g abort time is mainly when I have a composite background. Also the long finalizing time at the end of the rendering.

[Builtdown]

This is pretty ridiculous.
I have a scene that I rendered in 5k resolution. It has a coomposited background. Rendering took about an hour. But from 99% to final render, it took also about an hour to finalize the render.
After 15 minutes of waiting I would have liked to abort task, but then I would have to re-render the scene...

[juanjgon]

And are you sure that if you remove the background or any other LW compositing functions the render works fine? I've found that the render can be a bit slower if the compositing functions are enabled, but I can't understand the final delay of about 1 hour!

Thanks,
-Juanjo

[Builtdown]

It might have helped when I un-tagged one GPU to "use for tonemap".
I have three GTX1070 cards and now only one is "used for tonemap".

Do you think it might have helped with the Composited BG slowness?

[juanjgon]

Perhaps with this option disable on some GPUs less compositing operations are needed.

Thanks,
-Juanjo

[juanjgon]

For the next build (that I'll release in few days), I've added an option to disable the preview image while rendering using F9/F10. This should improve the rendering performance of scenes with large render resolutions or with the LW compositing functions enabled. Please test it with your scenes to see how it works.

Thanks,
-Juanjo