On 1/15/07, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Nobody yet gave any reasonable explanation why we are that fast on Mac OSX compared to any other allocator. Recall, that was 870.573/70.713.324 ops/sec Zippy/VT so about 81 times faster, for 16 threads. Although it really seems like a bug either in the testcode or in the allocator, I have not been able to verify any. All is working as it should. So, the mistery remains...
Because Mac OSX SucksMonkeyBawlz() in a tight inner loop? The engineers at Apple have many fine achievements, but this kind of system level performance isn't one of them. All the benchmarks I've ever seen show that SucksMonkeyBawlz() is sprinkled throughout the code responsible for locking, context switching, memory allocation, etc. So, don't be surprised. Enjoy the drop shadows!
