[mpich-discuss] Very long configuration time

Yida Wang yidawa at gmail.com
Wed May 21 15:35:42 CDT 2014

I have to use icc since I want to run code on Intel Xeon Phi. Also, I tried
to install MPICH2 since it claims to support Intel-MIC architecture and is
open source.

BTW, still configuring. It's faster to do it locally (both the source code
and the Intel compiler), but encountered a Fortran type length detection
error (don't remember the exact error information now, it recommended me to
"Consider setting CROSS_F77_SIZEOF_INTEGER to the length in bytes of a
Fortran INTEGER") last run.


On Wed, May 21, 2014 at 4:28 PM, Jed Brown <jed at jedbrown.org> wrote:

> Kenneth Raffenetti <raffenet at mcs.anl.gov> writes:
> > The Intel compilers could also be a source of slowdown. Are they
> > installed on a network filesystem? They may also call out to a network
> > license server each time they are invoked for a compile test. Does just
> > compiling a small program take a long time with icc, ifort, etc.?
> The system headers and libraries are also often on a network file
> system.  Although moving the source tree to a local disk usually
> provides some improvement, I rarely find it getting anywhere close to
> the performance of a cheap laptop because most of the file accesses
> performed by the compiler are hitting the network anyway.  This is the
> price we all pay for legacy file system semantics and dumb compiler
> architecture.  I think most companies in a place to change these things
> do full local installs on their development boxes so that compilation is
> fast.  And the HPC vendors wear blindfolds and put their heads in the
> sand.
> As for Intel license servers, this is the price you pay for anti-piracy
> measures.  People that are really ticked off by this crack their
> compilers---the pirates enjoy a better user experience.  Is it ethical
> to use a cracked version if you've already paid for the licensed
> version?
> Besides those issues, the Intel compiler usually takes a lot longer to
> compile.  It's worth building with gcc and clang to compare.  You might
> be pleasantly surprised to find that in addition to compiling faster,
> your code also runs faster (this is the case for several applications I
> work with).
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20140521/1b2f9b90/attachment.html>

More information about the discuss mailing list