[petsc-dev] Seeking OLCF users complaining about poor build times

[Barry Smith]

> On Feb 26, 2015, at 9:16 PM, Nathan Collier <nathaniel.collier at gmail.com> wrote:
> 
> Barry,
> 
> > Do you know where /tmp is on the system? Presumably it is fast?
> 
> I am not sure about that. There is a /tmp but I am not sure what it is or if/how I can use it.

   They never told you to do compiles on particular file systems or anything?  For example did they ever say DON'T compile on the lustre file system?

> 
> Also, I was the only one running anything on the login node when I did the configure/make. My configure does include the sowing download.

  You can run the exact same configure again (don't delete what is there) and this time it will use the sowing that is already there. My bet is it has very very little effect on the configure time.

  Barry

> 
> Nate
> 
> 
> On Thu, Feb 26, 2015 at 9:53 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> On Thu, 26 Feb 2015, Nathan Collier wrote:
> 
> > Ok, so I am not sure I got all that, but here goes some more information
> > (attached log).
> >
> > No packages / master
> >
> > [nate at titan] time python no_packages.py
> > ...
> > real 14m32.169s
> > user 1m51.527s
> > sys 3m40.734s
> >
> > [nate at titan] time make all
> > ...
> > real 15m56.004s
> > user 8m8.971s
> > sys 52m42.734s
> 
> BTW: This number for 'make all' looks bizzare [or I don't know how to interpret it].
> 
> - 'sys' time is 52m?
> - 'user' time is 8m - but 'real' is 15m - so its not a parallel build?
>    But configure sets 'MAKE_NP = 24' (with gnumake build).
> 
> Perhaps its all intel compiler license server overhead? :)
> 
> Satish
>