Author Topic: Render times  (Read 13515 times)

2018-11-23, 16:30:21

ozwald

  • Active Users
  • **
  • Posts: 147
    • View Profile
Hello team, I hope you are very well.
I'm writing for the next topic.

The other day I had to deliver a render to a client of 190cm x 240cm
The work was done in Corona B2. noise level 6
rendering time 32 hours

For that reason I had to stop the render and change the render engine.

For the commercial render your work times will improve?
It's good to know that we can expect to have the commercial version.

Here I did some comparative tests on render times

2018-11-23, 23:29:49
Reply #1

BigAl3D

  • Active Users
  • **
  • Posts: 879
    • View Profile
Just to clarify, your large render you say is 190cm x 240cm. What resolution is that? Is that 72dpi at 5,385 pixels wide or 300dpi at 22,200 pixels wide? Just so we know what you're dealing with. Did you change to Vray? What time was "acceptable" after you changed the render engine? I find many people don't understand the final use of digital files and go overboard with the render settings.

For example, an image used on a billboard along a road will be viewed from at least 100 feet away if not more. You can get away with VERY low resolutions and high noise levels. When you're that far way, your eyes blend it all together. Certain types of printing have the same issues. Always make sure you speak with a production person who will use your final artwork.

2018-11-24, 01:01:29
Reply #2

HFPatzi

  • Active Users
  • **
  • Posts: 138
    • View Profile
For comparison: Most of the time i render 9000 x 6000 pixels @72dpi. Since these are Converted CAD-Files my polycount is quite large. Between 3000000 and 6000000. This being said, My rendertimes vary between 2 to 6 hours at a noise level between 1 and 2 before denoising.

So I guess you are rendering 190cm x 240cm @300 dpi, and for that size, 32 hours in my opinion is not too bad.
How many Renderclients did you use?

2018-11-24, 03:05:27
Reply #3

ozwald

  • Active Users
  • **
  • Posts: 147
    • View Profile
For comparison: Most of the time i render 9000 x 6000 pixels @72dpi. Since these are Converted CAD-Files my polycount is quite large. Between 3000000 and 6000000. This being said, My rendertimes vary between 2 to 6 hours at a noise level between 1 and 2 before denoising.

So I guess you are rendering 190cm x 240cm @300 dpi, and for that size, 32 hours in my opinion is not too bad.
How many Renderclients did you use?

Thanks for comment
ok, I explain myself well.
I know that the images that go to big impressions the pixels go down to 36 or less on their real size.
I have been working on this for years and I have some knowledge about it.

About the image that I speak here is 190 centimeters by 240 centimeters
to a resolution of 72dpi, since it goes in an internal window of a store
and you will see less than 1 meter.

this theme if we take it to pixels would be 5385pixels for 6803 pixels.
As you know, it's not an exaggerated size
The noise level that I put is 5
After 2 hours of analyzing the engine he said that the estimated time would be 32 hours.
So I stopped the work and changed the render engine.

So simple that I did the leather chair test, where
there you can see the results.

2018-11-24, 14:00:44
Reply #4

mitchino

  • Active Users
  • **
  • Posts: 86
    • View Profile
Wow, normally I find Corona to be be faster than vray. Have to also say the vray chair looks more realistic to my eyes.

2018-11-24, 14:20:59
Reply #5

HFPatzi

  • Active Users
  • **
  • Posts: 138
    • View Profile
Thanks for you explanation. Thats kinda strange. An image that size should not take that long, especially at this noise level. Did you have a low-ram-warning or checked your ram usage while rendering? And what are your machine's specs?

2018-11-24, 16:44:59
Reply #6

ozwald

  • Active Users
  • **
  • Posts: 147
    • View Profile
It is the first time that I make a comparison of renders.
But I realized that when there is grass or hair in the scene, the crown motor takes a long time.
I do not know if the rendering delay is because of the small carpet that is in the scene.
In short I do not know what could happen in that scene.

But!! the scene of the chairs we noticed a great difference of time.
Apart from the quality of the result, the rendering time is very importan
« Last Edit: 2018-11-24, 16:49:19 by ozwald »

2018-11-27, 09:10:09
Reply #7

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
It also seems to me that the last two versions work 1x slower then before.
From old 3h render time to new 6h render time.

2018-11-28, 16:20:53
Reply #8

ozwald

  • Active Users
  • **
  • Posts: 147
    • View Profile
All the topics that we expose in the forum are important.
The render time in my opinion is very important.

I hope someone from the team can make a comment.
Renders of products for interior decoration where the client demands
sharpness in the details ........... is where the corona rendering times are high.

2018-11-29, 00:01:26
Reply #9

Ealexander

  • Active Users
  • **
  • Posts: 170
    • View Profile
    • evan alexander
Overall, your render times seem really slow, but yes, if you are rendering large format sizes, that is going to take some time, no matter what render engine. 16 minutes on that chair leather seems slow too, so I would ask: what is your scene optimization like and what are your hardware specs?  Are you using a quad core laptop or a 18 core tower? Is your scene full of parametric generators (nested sweeps, boolean, subdivision objects, symmetry, Clones)? This can have a huge effect on how the scene is handled by any engine. I do big scenes with lots of objects (but usually only 2500 px wide) and Corona rips through it. So I'm curious about your hardware setup first.
« Last Edit: 2018-11-29, 00:05:03 by Ealexander »

2018-11-29, 07:50:36
Reply #10

Beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 3811
  • Bengamin
    • View Profile
    • Cormats
You could also try unchecking "Use new implicit conversion" in the developer settings to see if that helps.
Bengamin Jerrems l chaos-corona.com
3D Support Specialist - Corona l contact us
Corona Uploader l Upload
Portfolio l Click me!

2018-11-29, 15:34:35
Reply #11

Beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 3811
  • Bengamin
    • View Profile
    • Cormats
It also seems to me that the last two versions work 1x slower then before.
From old 3h render time to new 6h render time.

Could you be more specific with the versions you are referring to? What was the scene you were rendering? I just completed two sets of tests both interior and exterior with RC1, 2, 3, 4 & B2 Final on R19 and R20 and the results were rather close. If your scene is available I'd love to try it. I'd also be interested to know how you set your pass limit, was it done by choosing a noise or a set pass amount? One other thing, was the sampler changed from DMC to another? As this will change the way noise is calculated.

Thanks,
Bengamin Jerrems l chaos-corona.com
3D Support Specialist - Corona l contact us
Corona Uploader l Upload
Portfolio l Click me!

2018-11-29, 16:02:11
Reply #12

ozwald

  • Active Users
  • **
  • Posts: 147
    • View Profile
Overall, your render times seem really slow, but yes, if you are rendering large format sizes, that is going to take some time, no matter what render engine. 16 minutes on that chair leather seems slow too, so I would ask: what is your scene optimization like and what are your hardware specs?  Are you using a quad core laptop or a 18 core tower? Is your scene full of parametric generators (nested sweeps, boolean, subdivision objects, symmetry, Clones)? This can have a huge effect on how the scene is handled by any engine. I do big scenes with lots of objects (but usually only 2500 px wide) and Corona rips through it. So I'm curious about your hardware setup first.

I do not use laptop, above is the description of the computer, with it big 3d design works are done

2018-12-02, 05:22:17
Reply #13

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
It also seems to me that the last two versions work 1x slower then before.
From old 3h render time to new 6h render time.

Could you be more specific with the versions you are referring to? What was the scene you were rendering? I just completed two sets of tests both interior and exterior with RC1, 2, 3, 4 & B2 Final on R19 and R20 and the results were rather close. If your scene is available I'd love to try it. I'd also be interested to know how you set your pass limit, was it done by choosing a noise or a set pass amount? One other thing, was the sampler changed from DMC to another? As this will change the way noise is calculated.

Thanks,
Hi,

I'm using the latest version: Build Oct 31 2018, B2 (core 3). Render is set to noise level limit 3 as usual, everything else is set to default with lightmix ON (with about 20 area lights) just sky&sun.
All projects are constantly very similar (residential), workflow is the same, setup is the same...maybe it's a feeling and it's weird scene or we make something wrong.
I'll send you a complete project file...I need to find the project that I can share and is not confidential.

Regards
« Last Edit: 2018-12-02, 05:31:09 by minimaldesign - Blaž »

2018-12-02, 17:14:56
Reply #14

Barendby

  • Active Users
  • **
  • Posts: 123
    • View Profile
To me corona is a great render engine but very slow. I come from many years in vray, both on max and then a few years in modo.
I could deliver a bedroom in an hour, rendered at 5000x3000 (plus minus) resolution. a restaurant or complex scene between 2 and 4 hours.
This all with Vray's excellent DR system, using 3x i7 - 5960x machines.
Corona crash out every time I use teamrender on a 5000x3000 resolution render, no warning. So I am forced to use one pc to render.
I "write off" the bad render times as I am not able to use all machines together, but honestly I also think Corona is way slower than vray. I would love to see more improvement on teamrender, maybe that can solve the issue