Hi, > On 10 Aug 2017, at 10:13, Christopher Sean Morrison <brl...@mac.com> wrote: > > Marco, > > I saw your benchmark logs and it looks like you ran the non-opencl version > three times, which is almost certainly why the performance rankings were > nearly identical. You’ll want to run “TIMEFRAME=60 DEVIATION=1 benchmark > run” for the non-ocl path and “TIMEFRAME=60 DEVIATION=1 benchmark run -z1” to > get the ocl path. It should show that additional -z1 rt option in the > summary log. >
Yes, at the time I ran three different benchmarks over the non-opencl version because I was trying to compare three different versions of the ANSI C code. This was, the ANSI C code currently in the trunk, the code in the trunk with the patch #473 applied (patch from Vasco that removed the gotos from the bool_eval(), and the ANSI C code in the opencl branch, which uses a boolean tree in postfix notation. But perhaps this is not the best approach to compare the performance. Well, at least I couldn’t really understand which number in the benchmark log I should look at to compare. Is is the “Total testing time elapsed” or the “VGR” metric? The “VGR” number didn’t make much sense, because the version that got higher VGR is the code in which the ‘rt’ command takes more time to run. Cheers! Marco > Vasco, > > Awesome TrueReg realization… I dug through the history and that surprisingly > goes all the way back, nearly to the beginning. Half-guessing as to the > intention but there’s a hint that it was going to be used to hand back more > information to callers for XOR and overlap cases where there is ambiguity. > Instead, it looks like a decision was made to simply rewrite the nodes and > handle them in other ways. Running a performance impact check now. > > 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 ------------------------------------------------------------------------------ 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
