Drop in performance with the last 3 daily builds

[CiroC]

ok, this looks definitely like a bug

But I can't find any logical explanation. Let me know if there is anything else you need.

[CiroC]

I am starting to get to the conclusion that Corona doesn't like Xref files.

If I Xref a scene the scene parsing and geometry gets really high (over 4 minutes). However, if I merge the scene the Geometry takes a little bit longer (1min or so), but the render starts really fast.

The problem I have is that this exterior scene is massive and have loads of trees and other vegetation.

The results from the experience I did:

Scene with no Xref
Scene Parsing  - 3 seconds
Geometry - 7 seconds

Scene with a Xref
Scene Parsing - 4 seconds
Geometry - 3:57 minutes

Scene with the merged Xref
Scene Parsing: 3 seconds
Geometry - 1:43

[CiroC]

I am working on another scene and I noticed the same behaviour.

It is a simple scene with 7350 scatter elements (grass) and maybe 10 trees. I start the render it takes 2 minutes to Scene Parsing and 3 minutes to Geometry. I stop the render and re-render again. The Scene Parsing drops to 25 seconds and the Geometry to 1 minute.

What bothers me is not even the Scene parsing and the Geometry time. The problem is that the Ray/s total and Ray/s actual are very low which makes the render taking ages.

Ondra, do you want this scene as well?

[Ondra]

yes, it couldnt hurt to have more samples ;)

[Ondra]

CiroC: it renders fine here... it may be simple memory exhaustion... how is your system memory during rendering?

BTW: we are implementing a Corona warning that will pop out once you start running out of memory.

[Ondra]

also it seems camera is squished flat in the scene you uploaded... do you also see it?

[VASLAVO]

We have similar issues and also disapearing parts of proxys, also if you hit render it says 22 hours and if you stop and hit again render it says 255 hour and for the proxy only it took 30 min for 6 passes at 2800 pixels wide, here an example. Did the test with and no forest, same results, testet on machines with 64 gigs of ram and 32, i7 and dual xeon and sinlge xeon, same results.

[CiroC]

CiroC: it renders fine here... it may be simple memory exhaustion... how is your system memory during rendering?

BTW: we are implementing a Corona warning that will pop out once you start running out of memory.

also it seems camera is squished flat in the scene you uploaded... do you also see it?

Thanks Ondra for the feedback.
I am attaching a screenshot of the memory used during the render (it is using 14.2GB from 16GB). What is strange is that the CPU is only between 1% and 4%. Does it sound right?

Yes the camera is weird because we are trying to encompass a big area. But if I am not wrong is something possible with a tilt lens. :D

I am going to pack the other scene and upload it.

[CiroC]

Hi Ondra.

I uploaded another file called Civils. This one doesn't take too long to render, but it is same thing I mentioned. The Scene Parsing and Geometry take something around 5 or 7 minutes, but if you stop and press render again, the Scene Parsing and Geometry goes back to 1 or 2 minutes.

Plus, I tried to render a simple a scene I can see the CPU going to 90%. When this "issue" happens the CPU doesn't go higher than 6%.

[CiroC]

We have similar issues and also disapearing parts of proxys, also if you hit render it says 22 hours and if you stop and hit again render it says 255 hour and for the proxy only it took 30 min for 6 passes at 2800 pixels wide, here an example. Did the test with and no forest, same results, testet on machines with 64 gigs of ram and 32, i7 and dual xeon and sinlge xeon, same results.

I use loads of proxies. Could it be a problem with that? Usually, I use a combination of scatter and proxies.

I am going to try and convert the scatter objects into Max Geomtry and see if there is any change on speed.

[Ondra]

CiroC: it renders fine here... it may be simple memory exhaustion... how is your system memory during rendering?

BTW: we are implementing a Corona warning that will pop out once you start running out of memory.

also it seems camera is squished flat in the scene you uploaded... do you also see it?

Thanks Ondra for the feedback.
I am attaching a screenshot of the memory used during the render (it is using 14.2GB from 16GB). What is strange is that the CPU is only between 1% and 4%. Does it sound right?

Yes the camera is weird because we are trying to encompass a big area. But if I am not wrong is something possible with a tilt lens. :D

I am going to pack the other scene and upload it.

ok, this definitely looks like memory exhaustion. With fewer objects the scene should render fine. I will looka t the other one though

[CiroC]

Many thanks Ondra.

I will try your suggestion.

[CiroC]

Hi Ondra,

One thing related with this issue, is that when I press the Stop or Cancel button Corona stills carry on calculating the Scene Parsing or the Geometry, which in this situation can take 10 minutes. Is that a bug?

[Ondra]

that is probably also because you are out of memory and your system is swapping everything

[VASLAVO]

Hi Ondra, we check on every machine and the cpu usage its arround 2 or 5 %, only the dual xeons are using 99 to 100%, it doesnt matter if its a tree or a bunch of them, its like its trying to render only with ram, the other thing its that the proxys created with this daily version are unreadable with 1.21 and those proxys are missing some elements ramdomly when render (daily not 1.21).