What is going on with those results? In both cases the first parallel code is seriously outperforming the single-core. I'd be interested in seeing the two log_summary outputs. I can only assume that the PETSc developers have an (if (serial); sleep(10);) buried somewhere in the src from their last Gordon Bell run :) A On Thu, Apr 11, 2013 at 6:33 PM, Chris Kees <[email protected]> wrote:

Thanks a lot. I did a little example with the Bratu problem and posted it here:

https://proteus.usace.army.mil/home/pub/17/

I used boomeramg instead of geometric multigrid because I was getting an error with the options above:

%mpiexec -np 4 ./ex5 -mx 129 -my 129 -Nx 2 -Ny 2 -pc_type mg -pc_mg_levels 2 [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Argument out of range! [0]PETSC ERROR: New nonzero at (66,1) caused a malloc! [0]PETSC ERROR: ------------------------------------------------------------------------

I like the ice paper and will try to get the contractor started on reproducing those results.

-Chris

On Wed, Apr 10, 2013 at 1:13 PM, Nystrom, William D <[email protected]> wrote:

...

Sorry. I overlooked that the URL was using git protocol. My bad.

Dave

________________________________________ From: Jed Brown [[email protected]] on behalf of Jed Brown [ [email protected]] Sent: Wednesday, April 10, 2013 12:10 PM To: Nystrom, William D; For users of the development version of PETSc; Chris Kees Subject: Re: [petsc-dev] examples/benchmarks for weak and strong scaling exercise

"Nystrom, William D" <[email protected]> writes:

...

Jed,

I tried cloning your tme-ice git repo as follows and it failed:

% git clone --recursive git://github.com/jedbrown/tme-ice.git tme_ice Cloning into 'tme_ice'... fatal: unable to connect to github.com: github.com[0: 204.232.175.90]: errno=Connection timed out

I'm doing this from an xterm that allows me to clone petsc just fine.

You're using https or ssh to clone PETSc, but the git:// to clone tme-ice. The LANL network is blocking that port, so just use the https or ssh protocol.