Equinox3D for IRIX

[Irinikus]

It just took 5.7 seconds to render on my Mac Pro 2013!

This test scene in actual fact has very similar performance to test.blend in Blender.

 

[Irinikus]

Rendered again, this time 1280x1024 instead of 1280x960. All 16 CPUs (600MHz R14k, 4GB shared RAM) and it took 2 minutes 36 seconds.
All CPUs are showing load (although never 100%). At the end it does not render faster..1280x960 still had the same time as with just 12 CPUs.

On the fuel with just one 600MHz R14k CPU it shows 10% progress after 10 minutes. (still rendering)

Rendered in 5.61 seconds on my (dated) Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz with 4 cores.

Those are pretty interesting results! It seems as though it favours fewer cores at a higher clock speed!

 

[flexion]

Results on the Octane2 with 2x 300MHz R12k: 7 minutes 14 seconds

I'm still puzzled why the Fuel with one CPU 600MHz R14k needs ~ 1 hour 40 minutes!?!
and the Octane 2 with two 300MHz R12k takes just 7 minutes 14 seconds ??

That's a huge difference.. just like your first attempt on the tezro which also took more than one hour if I understood you right, but with a different app version. something must be wrong here.

Maybe I'll try again tomorrow with 3 GB RAM in the octane2 instead of just 1.5 GB to see if this also makes a difference.

 

[Irinikus]

My first attempt was made on a very early version that could only make use of one of the Tezro's CPU's, I suppose it was also very poorly optimised.

 

[flexion]

I have tried again on the Octane2 (dual 300MHz R12k) with more RAM:
1.5 GB RAM: 7 minutes 14 seconds
3.5 GB RAM: 6 minutes 59 seconds

 

[Irinikus]

That's surprising, as I wasn't expecting a difference!

 

[Irinikus]

It just took 3minutes and 51 seconds on my Octane 2 with dual R14K's@600MHz with 2GB of RAM. (First attempt)

The second attempt resulted in the exact same time of 3 minutes and 51 seconds, so it's pretty stable!

 

[flexion]

At the end rendering time was almost identical. That small difference was my fault, I forgot that I had osview running and another app silently eating up some more cpu cycles in the background. But I wanted to try it anyway, because I still don't get why it takes almost 2 hours on the fuel where I had just 1 GB RAM, and only one CPU, but takes a multiple of the time!

 

[Irinikus]

That's pretty strange indeed!

 

[flexion]

Indigo2 IMPACT R10k 195MHz 384MB RAM: 27 minutes 42 seconds

 

[flexion]

and finally also on the 600MHz R14K Fuel acceptable rendering times! deleted everything and started from scratch.

7 minutes 17 seconds

 

[Irinikus]

Cool!

 

[gijoe77]

I've come across a simple way to keep equinox3D from crashing on my o2. If the first thing you try to do is render using the Ray-tracer, it all just bombs out.

I launched ./eqx, then I loaded Irinikus's Sphere file. I brought up the rendering setup, and selected "shaded solid"as the renderer, and resolution of 320x256. I then hit render frame.

It seems using these other renderers first, seem to stabilize the ray-tracer. I've tried "shaded solid", I've tried "Hidden line". Key is use anyone first before using the ray-tracer

The program didn't find the concrete picture, so I had to point it to the file

so for the 320x256 render, it took 1m25s - on my o2 - pretty nice.


a 800x640 render took 8m17s

 

[Irinikus]

Very nice!

To keep all things equal, try to render the scene @ 1280x1024 with the concrete texture mapped.

 

[gijoe77]

21min on my trusty o2! Still a beast!

 

[Irinikus]

Cool!

Thanks!

 

[flexion]

21min on my trusty o2! Still a beast!

oh wow, on the O2? specs? R10k?

 

[gijoe77]

oh wow, on the O2? specs? R10k?

yes - 400mhz R12k with 1GB RAM