Safari.app benchmark - it ain't my problem

At least it looks like it. I seem to spend all my time in the routine that fetches a new page from memory and formats it for allocation. What is actually happening is that Mac OS X is busy zerofilling pages all the time. Running both benchmarks side by side I see with top -a

 PID COMMAND      %CPU   TIME    FAULTS   PAGEINS  COW_FAULTS MSGS_SENT  MSGS_RCVD  BSDSYSCALL MACHSYSCALL CSWITCH
 1289 Mulle        13.7%  0:04.23  3998     0        0          387        387        13245      387         1564
 1293 Apple         7.1%  0:04.92  4244     0        0          1256       1256       13245      1256        1784

As you can see at the end of the run, the Mullocator actually allocated less pages (FAULTS) and did much less Mach Calls, which is good. But speedwise I am still stuck around 60%. I suspect I will not convince the Darwinists that zero filling pages on a consumer machine is a waste of effort. :)

COW_FAULT (mooh) is a copy on write fault by the way, just looked it up.