Page 1 of 1

V2.03 Vs. 1.1.18

Posted: Sun May 03, 2009 9:25 am
by Rafaello
Well I have some test results with a core 2 quad Q6660 4 Gb Ram:

Indigo 2.03 10 hours 20 minutes 4,236 samples/s

Image



Indigo 1.1.18 10 hours 12 minutes 142,075 samples/s

Image

for me 2.03 is too slower

Re: V2.03 Vs. 1.1.18

Posted: Sun May 03, 2009 9:46 am
by Zom-B
This are some hard Numbers Rafaello and even harder images :(

For me the 64 bit Build was about 13% slower on a quick 100 spp test, maybe the 32bit build is more evil here?!

Afaik Ono did a bunch of SSE related optimizations for the 2.xx build... maybe something went terribly wrong there! Since Ono is on a 64bit Vista too, he maybe don't recognized this...

More Benchmarks would be nice here guys, keep them coming!

Re: V2.03 Vs. 1.1.18

Posted: Sun May 03, 2009 10:08 am
by Rafaello
I work in Xp 64 and feel so sad either, I hope Ono and Benn can think about continue the developement of 1.1.18 for the commercial purposes aswell, I think everyone want great images in less time.
I don't know about speed and quality in simple scenes, this one has nearly 8 million vertices.

Re: V2.03 Vs. 1.1.18

Posted: Sun May 03, 2009 11:53 am
by OnoSendai
Hi Rafaello,
Can you send me the scene so I can analyse it?
How big is the scene in MB?
If it's smaller than 5MB you could send it to nick@indigorenderer.com
thanks.

Posted: Sun May 03, 2009 4:56 pm
by Guest
Sorry Ono the files of the igs scene are 91 Mb big and the C4D scene is 99 Mb, so I can't send you the files by email. I will try to upload the files to rapidshare monday morning (here in México).

Posted: Sun May 03, 2009 5:00 pm
by Rafaello
I don't know why the last post appeared as guest, the post is mine. I will make some tests with a little light scene an will tell you what happens.

Re: V2.03 Vs. 1.1.18

Posted: Mon May 04, 2009 2:39 pm
by OnoSendai
Hi Rafaello,
Yup, it would be great if you could upload the file to rapidshare or something similar, like http://drop.io/

Thanks!

Re: V2.03 Vs. 1.1.18

Posted: Sun May 10, 2009 2:31 pm
by OnoSendai
This bug was fixed in version 2.0.5, thanks for bug report Rafaello!

Posted: Sun May 10, 2009 3:03 pm
by Rafaello
Happy to be usefull :wink: