Well, you were right about it being a spinlock issue (95% of the
profile) when running two threads. The problem is being spent in the
function lam_tv_load_type_defs. I'll include the shark profile. I
also tried leaving the program running over night on two threads, which
it should finish around 430s, but after 17 hours, it was still running.
Both processors are being used, but only one thread is active and
being passed between the two. The other thread starts up and then
doesn't do anything. There was no use in trying to do it with one
thread since the thread stays inactive. On another note, which version
of LAM/MPI uses the mpirun_ssh command if any does at all?
--
Jonathan Herriott
Architecture and Performance Group
Apple Computer, Inc.
408-974-5931
|
