While doing some performance tuning on a driver, I noticed that darwin-x86 is significantly slower than darwin-ppc on roughly equivalent hardware. When doing some pretty common operations (like running "sum <600 MB file>") most of the system time is charged to the kernel (e.g. kernel_task). If I wanted to profile the kernel and try to narrow down the sections of code that are problematic, how would I go about doing this? Is it safe to assume that 2-machine debugging is a necessary prerequisite? Is there any chance that the tools Apple uses internally for this operation will see the light of day? If this is NOT feasible, can any Apple kernel engineers suggest places in the code that could use some scrutiny? Any and all suggestions are welcome. cr _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.