Every time you run poly, it does a memory access that causes a memory fault, which it then handles and recovers from - a perfectly reasonable way to do its memory management, I would say.
Unfortunately, on Mac OS X, the memory fault triggers a crash log to be generated, and this causes quite an overhead (about 30% of the CPU time in my ProofPower build which runs poly a few hundred times). On Mac OS X 10.2, you could turn this off with the Console utility preferences, and that claws back the lost CPU, but you can't do this on Mac OS X 10.3.
Has anyone got a work-around for this? I consider it to be a bug in Mac OS X and would report it to Apple if I had a simple program to demonstrate the problem (but the technique Poly/ML is using is quite a hard one, so that's not trivial).
Regards,
Rob.