I would very much appreciate if people could grab the code from this pull 
request, and run:

        build/ARCH/libOpenImageIO/atomic_test
        build/ARCH/libOpenImageIO/spinlock_test

and report the timings after a fresh compile with USE_TBB ON, and again with 
USE_TBB OFF.  (On Linux and OSX, if you prefer running from 'make', then just 
run 'make nuke ; make USE_TBB=1' or 'make nuke ; make USE_TBB=0'.  On Windows, 
or if you prefer otherwise, just set the CMake variable USE_TBB to ON or OFF, 
respectively.)

I'm especially keen to hear the results from people on Windows, as that is the 
major platform that I have no way to test myself.

If this makes it appear that there is no speed penalty from falling back on the 
gcc & win32 intrinsics, compared to TBB, then I think we should simplify our 
lives by removing TBB use entirely from OIIO.



On Apr 3, 2012, at 10:25 AM, Larry Gritz wrote:

> Make atomic_test and spinlock_test run for many more iterations, and time 
> their results.
> 
> This allows us to rigorously compare the speed of our atomics and spin locks.
> Also make their output a little neater by locking around the status 
> printouts, and
> eliminate the #if's that provide safety for Boost < 1.35, which is no longer 
> supported.
> 
> You can merge this Pull Request by running:
> 
>  git pull https://github.com/lgritz/oiio lg-atomic
> 
> Or you can view, comment on it, or merge it online at:
> 
>  https://github.com/OpenImageIO/oiio/pull/273
> 
> -- Commit Summary --
> 
> * Make atomic_test and spinlock_test run for many more iterations, and time 
> their results.
> 
> -- File Changes --
> 
> M src/libOpenImageIO/atomic_test.cpp (38)
> M src/libOpenImageIO/spinlock_test.cpp (29)
> 
> -- Patch Links --
> 
>  https://github.com/OpenImageIO/oiio/pull/273.patch
>  https://github.com/OpenImageIO/oiio/pull/273.diff
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/OpenImageIO/oiio/pull/273
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

--
Larry Gritz
[email protected]


_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to