Page 2 of 5
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 11:14 am
by glimpse
gabrielefx wrote:do you want my 400Mb scene with 118 active textures to do a comparison?
The performance loss is exponential.
so, just to be clear, if I undestood You well, You're saying:
the heavier the scene becomes, more performance loss to expect?
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 11:48 am
by remKa
On a simple interior scene, 8000 Maxsamples PathTracing
1.5 : 7.5 MSamples/s almost 17 min
2.0 : 4.35 MSamples/s almost 31 min
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 1:49 pm
by RobSteady
gabrielefx wrote:The performance loss is exponential.
Very bad news
Do you have any numbers?
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 7:38 pm
by visionmaster2
same here...
almost 50% slower with 3xgtx780... wtf!
you say 10 to 25% slower...but even if it was true its too much.
there is no communication about it.
it's not on the news page when i purchase Octane update.
Otoy should tell us before buying the product.
it's good to list all the new features but you need to add a : be carefull, now with 2.0 octane is slower (up to 50%)
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 7:47 pm
by mykola1985
it's slower in complex scenes especially!!! displacement is amazing though!
Karba, can you create a kind of feature like: disable octane 2.0 features in order to improve performance?? or at least a possibility to switch between 2 versions: 1.5 - 2.0?
I think it would be great!!!
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 8:20 pm
by voon
This is kind of ironic ... most needed 2.0 feature: turn 2.0 off? I love thos enew features ... but the speed loss is crazy.
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 8:41 pm
by anifex3D
I would like to see some more users test scenes and post results between the 1.55 version and 2.0 version speeds. I am not sure I am believing the math on a 50% slowdown. I have tested several scenes here and the worst case scenario was about 24% slower. Other scenes were between 12%-20%.
I am not saying a slow down is ever going to be a good thing but I don't want nasty rumors to get out that Octane 2.0 is 50% slower because in my experience it is simply NOT TRUE and misrepresented statements like that could create bad press and slow down development on this render engine we all love.
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 8:55 pm
by voon
Also depends what's reported. Ms/s mean not much if more is accomplished per Ms. But I'm not sure how to compare this .. you'd have top go by "optical identity" to 1.5 rendering or soemthing of the benchmark scene.
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 9:06 pm
by emihich
I am facing a speed of 1.35 Ms/sec now instead of the 1.6 or more that I had before, with 1.5.
My interior scene machmoved animation will take Weeks to render, using PMC.
No one promissed speed improvement, but I wasn't expecting a worse performance.
I have the ORBX , My only hope is the Octane cloud to be easy enough soon .
There will be a direct link on the 2.0 interface next versions right ?
P.S : my video board is a fast and relatively expensive , nvidia Geforce GTX 780 Ti.
Re: Why v2.0 so slow ?
Posted: Tue Jun 10, 2014 9:26 pm
by charlesp2
Hey guys, I can confirm for sure it's slower, I'm working on a 1.6 million poly scene, just switched from 1.55 Max plugin to 2.0, same scene, speed went from 9.2M Samp/s down to 4.8M Samp/sec... This is an exterior scene with PMC.
So i installed 1.55 back on and I'm rendering as I type this lol. 2.0 needs some optimization before using it for production work or you'd rather get to sleep.
By the way I'm working on Dual GTX780's ...