On Tue, 06 May 2008 at 03:07AM -0700, mabshoff wrote: > IIRC you also saw quiet odd things happening with ptest.
That was on a different machine. I still have an account at the University of Minnesota and am ssh'ed into a computer there. (It happens to be the computer in my old office. :) > But even if pbuild is only running one thread at a time it should > still compile roughly as fast as setup.py since it is more or less > doing the exact same amount of work. So I am puzzled. Yeah, taking over an hour longer seems like something is really wrong somewhere. > What seems odd to me is that cpuinfo reports different CPUs: > > > model name : AMD Athlon(tm) MP 2600+ > > model name : AMD Athlon(tm) Processor > > Since that is generally not a good idea therein may lay your trouble. > I am sure that mixing and matching CPUs [i.e. MP with non-MP] is not > supported by AMD and it seems a sheer coincidence that your setup even > boots. Should they both be "AMD Athlon(tm) MP 2600+" CPUs then > something else hardware wise is probably broken. So in conclusion I > expect your hardware/software setup to be at fault here until proven > innocent :) I noticed that too, but it's the same model and stepping and all that. These computers were set up by the U of M math department IT staff, who really do know what they're doing. Those machines were bought as dual-processor machines, and I've run two large jobs on them simultaneously. I did try this: I started Sage (it's another copy on that machine) and factored some big number -- it took 11.95 seconds CPU time. Then in another shell, I started a big bzip2 job. Back in Sage, I factored the number again, and it took 13.2 seconds. That's a bigger penalty that I'd like to see, but both processors are clearly working. BTW, I ran 'make test' in the 3.0.1 tree and all tests passed (from the traditional build). Dan -- --- Dan Drake <[EMAIL PROTECTED]> ----- KAIST Department of Mathematical Sciences ------- http://math.kaist.ac.kr/~drake
signature.asc
Description: Digital signature
