> The first column (1.208s) is the time it takes over the code currently in the
> trunk (it uses a different bool_eval() function) and the 2nd column (2.198s)
> is the time taken from the OpenCL branch code (which uses the bool_eval()
> function with the boolean tree in RPN from Vasco).
Ah! Okay, thanks. That’s definitely way more than I would expect from the RPN
conversion… which you figured out why next.
>> Also, what’s the VGR number on your test machine? My laptop (~7K VGR)
>> renders havoc -s1024 in 0.39s (2.4M rays/s) …
>
> Okay so this difference in time made me go check if I was doing things
> correctly, and well, I wasn’t testing with a Release build… With the Release
> build I got 0.64s (rt -s1024) and 0.35s (rt -l5 -s1024, but this is a
> different lighting model from the one with the command ‘rt -z1 -l5’, as Vasco
> mentions in his email). This for the havoc scene with the view: az35, el25.
Unoptimized explains the 1.9x slowness. Have/Would you update all the table
values with optimized build numbers? Very informative.
> Is the VGR the number from the benchmark results? If that is the case then I
> got ~32k VGR on my machine.
That begs another question. My laptop is more than 4 times slower than your
machine, but my render times are a fraction of yours… I suspect you’re timings
are measuring something different.
If you’re using the timing block output from rt at the end, the important
number in the timing block is the RTFM line. That isolates just the ray trace
portion we care about.
Cheers!
Sean
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
