Comments on: More benchmark cheating http://gryniewicz.com/blogs/dang/2003/06/24/more-benchmark-cheating/ Tue, 10 May 2011 20:43:25 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Greg http://gryniewicz.com/blogs/dang/2003/06/24/more-benchmark-cheating/comment-page-1/#comment-35 Greg Thu, 01 Jan 1970 00:00:00 +0000 http://gryniewicz.com/blogs/dang/2003/06/24/more-benchmark-cheating/#comment-35 Not sure where you saw the info about the malloc implementation, but... It's not uncommon for compilers to use different allocators for the threaded and non-threaded cases. It's an obvious optimization: if you're compiling a non-threaded program, drop the locking overhead. I haven't been actually reading all the stories I've seen regarding Apple's cheating on benchmarks, but the ones I've seen so far seem to be just bitching; the benchmarks seem valid. Not sure where you saw the info about the malloc implementation, but… It’s not uncommon for compilers to use different allocators for the threaded and non-threaded cases. It’s an obvious optimization: if you’re compiling a non-threaded program, drop the locking overhead.

I haven’t been actually reading all the stories I’ve seen regarding Apple’s cheating on benchmarks, but the ones I’ve seen so far seem to be just bitching; the benchmarks seem valid.

]]>