> In your case - with 16 cores available - PETSc configure scheduled > 'make -j 13' job - and that ran for a bit more than a minute. And > 'user'+'sys'/'real' times give a factor of 6.2 - so thats equivalent > to keeping 6 cores 100% busy?
Ok, I wasn't aware that you were tuning the build process. I was just using the downloaded release, not the github master. Github pull, only optimization options, using MKL: real 5m10.249s user 2m15.844s sys 2m2.092s real 1m28.763s user 7m50.110s sys 1m55.301s
