Intel® MPI Library

Making applications perform better on Intel® architecture-based clusters with multiple fabric flexibility

  • Performance Optimized MPI Library
  • Sustained Scalability – Low Latencies, Higher Bandwidth & Increased Processes
  • Full Hybrid Support for multicore & manycore systems

$499.00
Buy Now

Or Download a Free 30-Day Evaluation Version

Deliver Flexible, Efficient, and Scalable Cluster Messaging

Intel® MPI Library 4.1 focuses on making applications perform better on Intel® architecture-based clusters—implementing the high performance Message Passing Interface Version 2.2 specification on multiple fabrics. It enables you to quickly deliver maximum end user performance even if you change or upgrade to new interconnects, without requiring changes to the software or operating environment.

Use this high performance MPI message library to develop applications that can run on multiple cluster interconnects chosen by the user at runtime. Benefit from a free runtime environment kit for products developed with Intel® MPI library. Get excellent performance for enterprise, divisional, departmental, workgroup, and personal High Performance Computing.


Intel® MPI Library (Intel® MPI) provides reduced MPI latency which can result in faster throughput.
Click to enlarge

Top Features

  • Scalability Up To 120K Processes
  • Industry Leading Latency Performance
  • Interconnect Independence & Flexible Runtime Fabric Selection


Quotes

“Fast and accurate state of the art general purpose CFD solvers is the focus at S & I Engineering Solutions Pvt, Ltd. Scalability and efficiency are key to us when it comes to our choice and use of MPI Libraries. The Intel® MPI Library has enabled us to scale to over 10k cores with high efficiency and performance.”
Nikhil Vijay Shende, Director,
S & I Engineering Solutions, Pvt. Ltd.

Scalability

  • Scaling up to 120k Processes
  • Low overhead allows random access to portions of a trace, making it suitable for analyzing large amounts of performance data.
  • Thread safety allows you to trace multithreaded MPI applications for event-based tracing as well as non-MPI threaded applications.
  • Improved start scalability through the mpiexec.hydra process manager

Industry Leading MPI Library
Click to enlarge

Industry Leading MPI Library
Click to enlarge

Performance

  • Low latency MPI implementation up to 6.5 as fast as alternative MPI libraries
  • Deploy optimized shared memory dynamic connection mode for large SMP nodes
  • Increase performance with improved DAPL and OFA fabric support
  • Accelerate your applications using the enhanced tuning utility for MPI
FeatureBenefit
Increased MPI Performance and Scalability

New connection manager and auto-selection methods increase scalability over RDMA-based interconnects.  Improved support for NUMA applications and addition of advanced process pinning controls allow development and deployment for continued capacity growth of HPC systems.

Extended Scalability on Windows*

The highly scalable Hydra Process Manager is now available for Windows*-based clusters.  Use mpiexec.hydra for enabling low-latency RDMA devices through Microsoft’s Network Direct* interface.

Extended support for the Intel® Xeon Phi™ Coprocessor

Native port of the Tag Matching Interface (TMI) over the Qlogic* PSM fabric.  Extending support for Checkpoint/Restart (BLCR*) on the Intel® Xeon Phi™ coprocessor.

Latest Processor Support
Haswell, Ivy Bridge, Intel® Many Integrated Core Architecture

Intel consistently offers the first set of tools to take advantage of the latest performance enhancements in the newest Intel product, while preserving compatibility with older Intel and compatible processors. New support includes AVX2, TSX, FMA3 and AVX-512.

Scalability

Implementing the high performance version 2.2 of the MPI-2 specification on multiple fabrics, Intel® MPI Library 4.1 for Windows* and Linux* focuses on making applications perform better on IA-based clusters. Intel® MPI Library 4.1 enables you to quickly deliver maximum end-user performance, even if you change or upgrade to new interconnects without requiring major modifications to the software or to the operating environment. Intel also provides a free runtime environment kit for products developed with the Intel® MPI library.

Performance

Optimized shared memory path for multicore platforms allows more communication throughput and lower latencies. Native InfiniBand interface (OFED verbs) also provides support for lower latencies. Multi-rail capability for higher bandwidth and increased interprocess communication and Tag Matching Interface (TMI) support for higher performance on Qlogic* PSM and Myricom* MX interconnects.

Intel® MPI Library 4.1 Supports Multiple Hardware Fabrics

Whether you need to run TCP sockets, shared memory, or one of many Remote Direct Memory Access (RDMA) based interconnects, including InfiniBand*, Intel® MPI Library 4.1 covers all your configurations by providing an accelerated universal, multi-fabric layer for fast interconnects via the Direct Access Programming Library (DAPL*) or the Open Fabrics Association (OFA*) methodology. Develop MPI code independent of the fabric, knowing it will run efficiently on whatever fabric is chosen by the user at runtime.

Additionally, Intel® MPI Library 4.1 provides new levels of performance and flexibility for applications achieved through improved interconnect support for Myrinet* MX and QLogic* PSM interfaces, faster on-node messaging and an application tuning capability that adjusts to the cluster architecture and application structure.

Intel® MPI Library 4.1 dynamically establishes the connection, but only when needed, which reduces the memory footprint. It also automatically chooses the fastest transport available. Memory requirements are reduced by several methods including a two-phase communication buffer enlargement capability which allocates only the memory space actually required.

Purchase Options

Several suites are available combining the tools to build, verify and tune your application. The products covered in this product brief are highlighted in blue. Named-user or multi-user licenses along with volume, academic, and student discounts are available.


Click to enlarge

Technical Specifications

Feature Benefit
Processor support

Validated for use with multiple generations of Intel® and compatible processors including but not limited to: 2nd Generation Intel® Core™2 processor, Intel® Core™2 processor, Intel® Core™ processor, Intel® Xeon™ processor, and Intel® Xeon Phi Coprocessors

Operating systems

Windows* and Linux*

Programming languages

Natively supports C, C++ and Fortran development

System requirements

Please refer to www.intel.com/software/products/systemrequirements/ for details on hardware and software requirements.

Support

A free Runtime Environment Kit is available to run applications that were developed using Intel® MPI Library

All product updates, Intel® Premier Support services, and Intel® Support Forums are included for one year. Intel Premier Support gives you confidential support, technical notes, application notes, and the latest documentation. Join the Intel® Support Forums community to learn, contribute, or just browse! http://software.intel.com/en-us/forums

Try Tools from Intel

Download a free 30-day evaluation from: http://intel.ly/sw-tools-eval. Click on ‘Cluster Tools’ link.

Scalability

Implementing the high performance version 2.2 of the MPI-2 specification on multiple fabrics, Intel® MPI Library 4.1 for Windows* and Linux* focuses on making applications perform better on IA-based clusters. Intel® MPI Library enables you to quickly deliver maximum end-user performance, even if you change or upgrade to new interconnects without requiring major modifications to the software or to the operating environment. Intel also provides a free runtime environment kit for products developed with the Intel® MPI library.

Performance

Optimized shared memory path for multicore platforms allows more communication throughput and lower latencies. Native InfiniBand interface (OFED verbs) also provides support for lower latencies. Multi-rail capability for higher bandwidth and increased interprocess communication and Tag Matching Interface (TMI) support for higher performance on Qlogic* PSM and Myricom* MX interconnects.

Intel® MPI Library 4.1 Supports Multiple Hardware Fabrics

Whether you need to run TCP sockets, shared memory, or one of many Remote Direct Memory Access (RDMA) based interconnects, including InfiniBand*, Intel® MPI Library 4.1 covers all your configurations by providing an accelerated universal, multi-fabric layer for fast interconnects via the Direct Access Programming Library (DAPL*) or the Open Fabrics Association (OFA*) methodology. Develop MPI code independent of the fabric, knowing it will run efficiently on whatever fabric is chosen by the user at runtime.

Additionally, Intel® MPI Library 4.1 provides new levels of performance and flexibility for applications achieved through improved interconnect support for Myrinet* MX and QLogic* PSM interfaces, faster on-node messaging and an application tuning capability that adjusts to the cluster architecture and application structure.

Intel® MPI Library 4.1 dynamically establishes the connection, but only when needed, which reduces the memory footprint. It also automatically chooses the fastest transport available. Memory requirements are reduced by several methods including a two-phase communication buffer enlargement capability which allocates only the memory space actually required.

Purchase Options

Several suites are available combining the tools to build, verify and tune your application. The products covered in this product brief are highlighted in blue. Single or multi-user licenses along with volume, academic, and student discounts are available.


Click to enlarge

Technical Specifications

FeatureBenefit
Processor support

Validated for use with multiple generations of Intel® and compatible processors including but not limited to: 2nd Generation Intel® Core™2 processor, Intel® Core™2 processor, Intel® Core™ processor, Intel® Xeon™ processor, and Intel® Xeon Phi Coprocessors

Operating systems

Windows* and Linux*

Programming languages

Natively supports C, C++ and Fortran development

System requirements

Please refer to www.intel.com/software/products/systemrequirements/ for details on hardware and software requirements.

Support

A free Runtime Environment Kit is available to run applications that were developed using Intel® MPI Library

All product updates, Intel® Premier Support services, and Intel® Support Forums are included for one year. Intel Premier Support gives you confidential support, technical notes, application notes, and the latest documentation. Join the Intel® Support Forums community to learn, contribute, or just browse! http://software.intel.com/en-us/forums

Videos to help you get started.

Register for future Webinars


Previously recorded Webinars:

  • Profiling MPI Communications - Tips and Techniques for High Performance
  • Increase Cluster MPI Application Performance with a "MPI Tune" Up
  • MPI on Intel® Xeon Phi™ coprocessor

Featured Articles:

Kein Inhalt gefunden

Seiten

More Tech Articles

Using Two DAPL Providers for MPI on Xeon Phi™
By James Tullos (Intel)Posted 12/05/20120
Update This article is outdated.  If you are using at least Version 4.1 Update 1 of the Intel® MPI Library, please go to http://software.intel.com/en-us/articles/using-multiple-dapl-providers-with-the-intel-mpi-library for updated information. Overview A feature is available for the Intel® MPI Libr…
Using MPI and Xeon Phi™ Offload Together
By James Tullos (Intel)Posted 12/03/20120
Overview Using the Intel® MPI Library along with the offload capabilities of the Intel® Xeon Phi™ coprocessor allows a user to access the capabilities of the coprocessor without the need for direct filesystem access on the coprocessor.  This can lead to administrative benefits by not requiring add…
Using the Intel® MPI Library in a server/client setup
By James Tullos (Intel)Posted 07/13/20123
A guide for using the MPI_Comm_accept and MPI_Comm_connect functions to form a server/client program suite with the Intel® MPI Library.
Partner Newsletter Q2 2011 Intel Cluster Ready Articles 2
By adminPosted 03/07/20120
Intel Cluster Ready Partner News - Q2-2011: Tips & Tricks - MPI Performance Tuning for Clusters and Applications, and Using Intel Cluster Checker for Post-Sales Support

Seiten

 abonnieren

Supplemental Documentation

Kein Inhalt gefunden

Seiten

 abonnieren

You can reply to any of the forum topics below by clicking on the title. Please do not include private information such as your email address or product serial number in your posts. If you need to share private information with an Intel employee, they can start a private thread for you.

New topic    Search within this forum     Subscribe to this forum


pmi_proxy stalls the HPC job
By Girish Nair3
Hi HPC enthusiasts, We are having a Sandy Bridge cluster of 8 nodes having the following: Hardware: 1U rackmount enclosure Intel S2400SC2 board 2 x Xeon E5-2450 processor 96GB ECC DDR3 RDIMM Intel True Scale QLE7340-CK HCA 500GB Enterprise SATA 36 port QLogic switch 24-port 1GbE switch Software: CentOS 6.2 x64 Intel MPI Library 4.1.1.036 Intel Fortran Composer XE 2013.3.163 NetCDF 4.0 FFTW 3.3.3 Open Grid Engine 2011.11.p1 NFS share Passphraseless SSH from any machine to any machine (meshed) Of late, whenever we submit the job (home-grown code) either via mpirun direct or through Grid Engine qsub, invariably (~90% times) the job does not start execution, it just appears to stay stalled. On inspection of process runs, we find that randomly few nodes shows 'pmi_proxy' with status 'D' (uninterruptible sleep). We have tested IMB (Intel MPI Benchmark), test codes (that comes with Grid Engine and Intel MPI) on the cluster both via mpirun and also through qsub, and it functi…
Segmentation fault in MPIU_Handle_obj_alloc_unsafe
By Victor V.3
Dear Developers, I am struggling with the following problem: [2] [2] ERROR: LOCAL:EXIT:SIGNAL: fatal error [2] [2] ERROR:    Fatal signal 11 (SIGSEGV) raised. [2] [2] ERROR:    Signal was encountered at: [2] [2] ERROR:       MPIU_Handle_obj_alloc_unsafe (/tmp/7b663e0dc22b2304e487307e376dc132.xtmpdir.nnlmpicl211.16412_32e/mpi4.32e.nnlmpibld05.20130522/dev/src/util/mem/x86_64/debug_dynamic/../../handlemem.c:353) [2] [2] ERROR:    While processing: [2] [2] ERROR:       MPI_Win_lock(lock_type=234, rank=2, assert=0, win=0xffffffffa0000002) [0] [0] WARNING: starting premature shutdown I got this diagnostic message by using the Intel ITAC. In our application we do a lot of 1sided passive "put" and "get" operations across working MPI processes. The memory attached to MPI's windows is allocated via 'malloc'. The program is running on the HP SL230s compute server equipped with two Intel E5-2660 (2.2 GHz Sandybridge) processors with 8 cores each (i.e. 16 cores per compute server).  The pro…
Windows cluster using ICS
By artret3
Hello everyone! I'm newbie in practical cluster computing and I want to create a cluster of 25 nodes on Windows 7 using Intel Cluster Studio. What do I need to accomplish this task? Just nodes with Win7 and ICS? Previously I tried to use cluster on Windows Server 2008 HPC and it had a cluster manager. Is there anything similar in ICS? Can I monitor nodes, their status and status of jobs? How do people create clusters on Windows? Can someone advise me articles or books to make things clearer? Thanks in advance.
Using MPI_Init_thread in one processor
By mullervki3
Hello, I have a very large external package I would like to use in my application. The package runs in parallel but only under MPI. To have users start the application under "mpirun ..." is impractical. However, there is a call - MPI_Init_thread - that appears equivalent to MPI_Init. So here's my question: can I continue building the application as I normally do then, say, on Windows, start multiple threads with _beginthreadex and, in each of the threads call MPI_Init_thread? In other words, would all subsequent calls to MPI behave as if I had a true multiprocessor run, except that functions such as MPI_Comm_rank would return the rank within this multi-threaded application, rather than in a multi-processor application? I'm trying to use this external package but will only run it on multi-core machines as multi-threaded. I'm hoping that all message passing will now be optimized for shared memory and I can use MPI transparently in a single processor application. Thanks. Arthur
MPI_Init crash after setting I_MPI_STATS
By vasci_9
After setting I_MPI_STATS=4, Intel MPI 4.1.3 on Linux crashes at MPI_Init *** glibc detected ***  free(): invalid pointer: 0x0000000002933384 *** ======= Backtrace: ========= /lib64/libc.so.6[0x3193e7164f] /lib64/libc.so.6(cfree+0x4b)[0x3193e7587b] [0x231e318] MPIR_Init_thread+0x62d)[0x231f7bd] (MPI_Init+0x218)[0x2313598]      
MPI run crashes on more than one node
By Sravan K.1
Hello, KInd Attn: James Tullos (Intel) I am facing a similar problem like http://software.intel.com/en-us/forums/topic/487208 and http://software.intel.com/en-us/forums/topic/280123#comment- My mpirun crashes giving the below error message. [proxy:0:4@cn004] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:70): assert (!(pollfds[i].revents & ~POLLIN & ~POLLOUT & ~POLLHUP)) failed [proxy:0:4@cn004] main (./pm/pmiserv/pmip.c:387): demux engine error waiting for event [mpiexec@hn1] HYDT_bscu_wait_for_completion (./tools/bootstrap/utils/bscu_wait.c:101): one of the processes terminated badly; aborting [mpiexec@hn1] HYDT_bsci_wait_for_completion (./tools/bootstrap/src/bsci_wait.c:18): bootstrap device returned error waiting for completion [mpiexec@hn1] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:521): bootstrap server returned error waiting for completion [mpiexec@hn1] main (./ui/mpich/mpiexec.c:548): process manager error waiting for completion I ha…
Erroneus [pmi_proxy] <defunct> left behind
By Nils M.1
My application makes heavy use of MPI_Comm_spawn calls to dynamically create and abandon processes. I am using Intel(R) MPI Library for Linux* OS, Version 4.1 Update 1 Build 20130522 on a Linux Cluster environment. Each subsequent call of MPI_Comm_spawn unfortunately leaves a  [pmi_proxy] <defunct> process behind, even if the subprocess has finished normally. These processes will be killed when the whole application finishes. They do not take in any resources. Since I make about 2000 MPI_Comm_spawn calls, these can become a serious and hard to detect bug if the OS reaches its file handle limit. Searching the Web gives certain results on the mpich bug tracker, namely ticket 670 and 1504 (spam filter prevents me from posting convenient links) and the mpich discussion board: http://lists.mpich.org/pipermail/discuss/2013-March/000515.html Could this still be an issue in the hydra implementation used by intel mpi? Thank you very much for your help!
MPI_Comm_spawn fails if called concurrently
By Nils M.1
I am using Intel(R) MPI Library for Linux* OS, Version 4.1 Update 1 Build 20130522 on a Linux Cluster environment. Running the following script will produce a race condition. All used libraries are compiled against this MPI library. from mpi4py import MPI comm = MPI.COMM_WORLD rank = comm.Get_rank() world_group = comm.Get_group() my_group = world_group.Incl([rank]) my_comm = comm.Create(my_group) intercomm = my_comm.Spawn("./script.sh", [], 1, MPI.INFO_NULL, 0) Randomly occuring error: [mpiexec@capp1] control_cb (./pm/pmiserv/pmiserv_cb.c:715): assert (!closed) failed [mpiexec@capp1] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status [mpiexec@capp1] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:430): error waiting for event [mpiexec@capp1] main (./ui/mpich/mpiexec.c:847): process manager error waiting for completion A possible workaround is given by serialization of the MPI_Comm_spawn calls: from mpi4py import MPI comm =…

Seiten

Foren abonnieren

Licensing

  • What kind of licenses are available for the Intel® MPI Library 4.1?
  • The Runtime license includes everything you need to run Intel MPI-based applications. The license is free and permanent. The Developer license includes everything needed to build and run applications. It is fee-based and permanent. It allows free redistribution of the components needed to run Intel MPI-based applications.

  • When is a Developer license required for the Intel® MPI Library 4.1?
  • The two kits (developer and runtime) can co-exist on a machine and it is fine for customers of Intel MPI-based applications to relink the application to include user subroutines. If the customer is actually writing MPI code (calling MPI_* functions directly), then a Developer license would be needed.

  • I am an ISV and am planning to ship my product with Intel MPI Library. Do my customers have to buy the Intel MPI Library Development Kit in order to use my software?
  • No. There are currently 3 different models if ISVs want to ship with Intel MPI Library.
    1) An ISV can redistribute the runtime components of the Intel MPI Library available from the development kit (see the redist.txt file in the Intel MPI Library installation directory for list of redistributable files).
    2) If a customer would rather install the Intel MPI Library as a system component, the Runtime Environment Kit can be downloaded free of charge from the Intel MPI Library product page.
    3) The Intel MPI Runtime Library can be pre-installed by the vendor and shipped with the application.

Downloads

Compatibility

  • Does the Intel® MPI Library 4.1 support 32-bit applications on 64-bit operating systems?
  • Yes. The Intel® MPI Library 4.1 supports 32-bit apps on 64-bit operating systems on Intel® 64.

  • Can the Intel® MPI Library 4.1 handle a mixed 32/64-bit job?
  • No. The Intel MPI Library does not support these types of heterogeneous configurations. All ranks of the job must be either IA-32, Intel® 64, or Intel® Many Integrated Core (MIC) Architecture based.

  • Is there a Microsoft* Windows* version of the Intel® MPI Library 4.1?
  • Yes. The Intel MPI Library 4.1 for Windows is available now.

  • Does the Intel MPI Library run on AMD platforms?
  • Yes. The Intel® MPI Library 4.1 is known to run on AMD platforms, and we have had no issue reports specific to AMD platforms so far.

  • Does the Intel® MPI Library 4.1 support parallel I/O calls?
  • Yes. The parallel file I/O part of the MPI-2 standard is fully implemented by the Intel® MPI Library 4.1. Some of the currently supported file systems include Unix File System (UFS), Network File System (NFS), Parallel Virtual File System (PVFS2), and Lustre*.  For a complete list, check the Release Notes.

  • Does the Intel® MPI Library 4.1 support one-sided communication?
  • Yes. The Intel® MPI Library 4.1 supports both active target and passive target one-sided communication. The only exception is the passive target one-sided communication in case the target process does not call any MPI functions.

  • Does the Intel® MPI Library 4.1 support heterogeneous clusters?
  • Up to a certain extent.  The Intel® MPI Library 4.1 does not support clusters running different operating systems.  But it does support an environment of mixed Intel processors and provides some default optimizations depending on the detected architecture.

  • What DAPL* version does the Intel® MPI Library 4.1 support?
  • The Intel® MPI Library 4.1 uses Direct Access Programming Library (DAPL) as a fabric independent API to run on fast interconnects like InfiniBand* or Myrinet*. Currently the Intel MPI Library supports DAPL* version 1.1, 1.2 as well as DAPL* version 2.0-capable providers. Intel MPI automatically determines version of DAPL standard to which the provider conforms.

  • What compilers does the Intel® MPI Library 4.1 support?
  • The Intel® MPI Library 4.1 supports Intel® Compilers 11.1 through 12.1 (or higher), as well as GNU* C, C++, Fortran77 3.3 or higher, and GNU* Fortran95 4.0 or higher. Additionally, the Intel® MPI Library 4.1 provides an unbundled source kit that offers support for the PGI* C, PGI* Fortran 77, and Absoft* Fortran 77 compilers out of the box, with the following caveats:

    • Your PGI* compiled source files must not transfer long double entities
    • Your Absoft* based build procedure must use the -g77, -B108 compiler option
    • You must take care of installing and selecting the right compilers yourself
    • You must make sure that the respective compiler runtime is installed on all nodes

    You may have to build extra Intel® MPI binding libraries if you need support for PGI* C++, PGI* Fortran 95, and Absoft* Fortran 95 bindings. If you need access to this additional binding kit, contact us via the Intel® Premier Support portal @ http://premier.intel.com

  • Does the Intel® MPI Library 4.1 work with any common resource managers?
  • Yes. The Intel® MPI Library 4.1 supports OpenPBS*, PBS Pro*, Torque, and LSF* job schedulers. The simplified job startup command mpirun recognizes when it is run inside a session started by any PBS compatible resource manager (like OpenPBS*, PBS Pro*, Torque*), as well as LSF*. See the Intel® MPI Library 4.1 Reference Manual for a description of this command.

  • I have a mixed application which uses both MPI and OpenMP* calls. Does the Intel® MPI Library 4.1 support this type of hybrid functionality?
  • Yes, Intel MPI does support mixed MPI/OpenMP applications.

Technical

  • Is the Intel® MPI Library 4.1 fault-tolerant?
  • Yes, to an extent. Note that the MPI standard does not yet define proper handling of aborted MPI ranks. By default, the Intel® MPI Library 4.1 will stop the entire application if any of the processes exit abnormally. This behavior can be overwritten via a runtime option where the library does allow for an application to continue execution even if one of the processes stops responding. Check the Intel® MPI Library 4.1 Reference Manual for details and application requirements.

  • Is the Intel® MPI Library 4.1 thread safe?
  • Yes. The Intel® MPI Library 4.1 introduces thread safe libraries at level MPI_THREAD_MULTIPLE since version 3.0. Several threads can make the Intel MPI Library calls simultaneously. Use the compiler driver -mt_mpi option to link the thread safe version of the Intel MPI Library. Use the thread safe libraries if you request the thread support at the following levels:

    MPI_THREAD_FUNNELED,
    MPI_THREAD_SERIALIZED, or
    MPI_THREAD_MULTIPLE.

    The previous versions of the Intel MPI Library provide only MPI_THREAD_NONE and MPI_THREAD_FUNNELED levels in terms of the MPI-2 standard.

  • How to learn what version of the Intel® MPI Library is installed on the system?
  • Provided you run the Intel® MPI Library 2.0.x, try running mpiexec –V:

    mpiexec –V
    This will output version information.

    If this is an official package, look up the mpisupport.txt file or the Release Notes and search for a version information there:
    cat /opt/intel/mpi/2.0.1/mpisupport.txt

    If Intel MPI has been installed in RPM mode, try to query the RPM database:
    rpm –qa | grep intel-mpi

    Finally, for full build identification information, set I_MPI_VERSION to 1 and run any MPI program, grepping for "Build":
    mpiexec –n 2 –env ./a.out | grep –i build
    This will turn up a couple of lines with the build date. Most of this information is also imbedded into the library and can be queried using the strings utility:
    strings /opt/intel/mpi/2.0.1/lib/libmpi.so | grep –i build

Licensing

  • What kind of licenses are available for the Intel® MPI Library 4.1?
  • The Runtime license includes everything you need to run Intel MPI-based applications. The license is free and permanent. The Developer license includes everything needed to build and run applications. It is fee-based and permanent. It allows free redistribution of the components needed to run Intel MPI-based applications.

  • When is a Developer license required for the Intel® MPI Library 4.1?
  • The two kits (developer and runtime) can co-exist on a machine and it is fine for customers of Intel MPI-based applications to relink the application to include user subroutines. If the customer is actually writing MPI code (calling MPI_* functions directly), then a Developer license would be needed.

  • I am an ISV and am planning to ship my product with Intel MPI Library. Do my customers have to buy the Intel MPI Library Development Kit in order to use my software?
  • No. There are currently 3 different models if ISVs want to ship with Intel MPI Library.
    1) An ISV can redistribute the runtime components of the Intel MPI Library available from the development kit (see the redist.txt file in the Intel MPI Library installation directory for list of redistributable files).
    2) If a customer would rather install the Intel MPI Library as a system component, the Runtime Environment Kit can be downloaded free of charge from the Intel MPI Library product page.
    3) The Intel MPI Runtime Library can be pre-installed by the vendor and shipped with the application.

Compatibility

  • Does the Intel® MPI Library 4.1 support 32-bit applications on 64-bit operating systems?
  • Yes. The Intel® MPI Library 4.1 supports 32-bit apps on 64-bit operating systems on Intel® 64.

  • Can the Intel® MPI Library 4.1 handle a mixed 32/64-bit job?
  • No. The Intel MPI Library does not support these types of heterogeneous configurations. All ranks of the job must be either IA-32, Intel® 64, or Intel® Many Integrated Core (MIC) Architecture based.

  • Is there a Microsoft* Windows* version of the Intel® MPI Library 4.1?
  • Yes. The Intel MPI Library 4.1 for Windows is available now.

  • Does the Intel MPI Library run on AMD platforms?
  • Yes. The Intel® MPI Library 4.1 is known to run on AMD platforms, and we have had no issue reports specific to AMD platforms so far.

  • Does the Intel® MPI Library 4.1 support parallel I/O calls?
  • Yes. The parallel file I/O part of the MPI-2 standard is fully implemented by the Intel® MPI Library 4.1. Some of the currently supported file systems include Unix File System (UFS), Network File System (NFS), Parallel Virtual File System (PVFS2), and Lustre*.  For a complete list, check the Release Notes.

  • Does the Intel® MPI Library 4.1 support one-sided communication?
  • Yes. The Intel® MPI Library 4.1 supports both active target and passive target one-sided communication. The only exception is the passive target one-sided communication in case the target process does not call any MPI functions.

  • Does the Intel® MPI Library 4.1 support heterogeneous clusters?
  • Up to a certain extent.  The Intel® MPI Library 4.1 does not support clusters running different operating systems.  But it does support an environment of mixed Intel processors and provides some default optimizations depending on the detected architecture

  • What DAPL* version does the Intel® MPI Library 4.1 support?
  • The Intel® MPI Library 4.1 uses Direct Access Programming Library (DAPL) as a fabric independent API to run on fast interconnects like InfiniBand* or Myrinet*. Currently the Intel MPI Library supports DAPL* version 1.1, 1.2 as well as DAPL* version 2.0-capable providers. Intel MPI automatically determines version of DAPL standard to which the provider conforms.

  • What compilers does the Intel® MPI Library 4.1 support?
  • The Intel® MPI Library 4.1 supports Intel® Compilers 11.1 through 12.1 (or higher), as well as GNU* C, C++, Fortran77 3.3 or higher, and GNU* Fortran95 4.0 or higher. Additionally, the Intel® MPI Library 4.1 provides an unbundled source kit that offers support for the PGI* C, PGI* Fortran 77, and Absoft* Fortran 77 compilers out of the box, with the following caveats:

    • Your PGI* compiled source files must not transfer long double entities
    • Your Absoft* based build procedure must use the -g77, -B108 compiler option
    • You must take care of installing and selecting the right compilers yourself
    • You must make sure that the respective compiler runtime is installed on all nodes

    You may have to build extra Intel® MPI binding libraries if you need support for PGI* C++, PGI* Fortran 95, and Absoft* Fortran 95 bindings. If you need access to this additional binding kit, contact us via the Intel® Premier Support portal @ http://premier.intel.com

  • Does the Intel® MPI Library 4.1 work with any common resource managers?
  • Yes. The Intel® MPI Library 4.1 supports OpenPBS*, PBS Pro*, Torque, and LSF* job schedulers. The simplified job startup command mpirun recognizes when it is run inside a session started by any PBS compatible resource manager (like OpenPBS*, PBS Pro*, Torque*), as well as LSF*. See the Intel® MPI Library 4.1 Reference Manual for a description of this command.

  • I have a mixed application which uses both MPI and OpenMP* calls. Does the Intel® MPI Library 4.1 support this type of hybrid functionality?
  • Yes, Intel MPI does support mixed MPI/OpenMP applications.

Technical

  • Is the Intel® MPI Library 4.1 fault-tolerant?
  • Yes, to an extent. Note that the MPI standard does not yet define proper handling of aborted MPI ranks. By default, the Intel® MPI Library 4.1 will stop the entire application if any of the processes exit abnormally. This behavior can be overwritten via a runtime option where the library does allow for an application to continue execution even if one of the processes stops responding. Check the Intel® MPI Library 4.1 Reference Manual for details and application requirements.

  • Is the Intel® MPI Library 4.1 thread safe?
  • Yes. The Intel® MPI Library 4.1 introduces thread safe libraries at level MPI_THREAD_MULTIPLE since version 3.0. Several threads can make the Intel MPI Library calls simultaneously. Use the compiler driver -mt_mpi option to link the thread safe version of the Intel MPI Library. Use the thread safe libraries if you request the thread support at the following levels:

    MPI_THREAD_FUNNELED,
    MPI_THREAD_SERIALIZED, or
    MPI_THREAD_MULTIPLE.

    The previous versions of the Intel MPI Library provide only MPI_THREAD_NONE and MPI_THREAD_FUNNELED levels in terms of the MPI-2 standard.

  • How to learn what version of the Intel® MPI Library is installed on the system?
  • Provided you run the Intel® MPI Library 2.0.x, try running mpiexec –V:

    mpiexec –V
    This will output version information.

    If this is an official package, look up the mpisupport.txt file or the Release Notes and search for a version information there:
    cat /opt/intel/mpi/2.0.1/mpisupport.txt

    If Intel MPI has been installed in RPM mode, try to query the RPM database:
    rpm –qa | grep intel-mpi

    Finally, for full build identification information, set I_MPI_VERSION to 1 and run any MPI program, grepping for "Build":
    mpiexec –n 2 –env ./a.out | grep –i build
    This will turn up a couple of lines with the build date. Most of this information is also imbedded into the library and can be queried using the strings utility:
    strings /opt/intel/mpi/2.0.1/lib/libmpi.so | grep –i build

Intel® MPI Library 4.1

Getting Started?

Click the Learn tab for guides and links that will quickly get you started.

Get Help or Advice

Search Support Articles
Forums - The best place for timely answers from our technical experts and your peers. Use it even for bug reports.
Support - For secure, web-based, engineer-to-engineer support, visit our Intel® Premier Support web site. Intel Premier Support registration is required.
Download, Registration and Licensing Help - Specific help for download, registration, and licensing questions.

Resources

Release Notes - View Release Notes online!
Intel® MPI Library Product Documentation  - View documentation online!
Documentation for other software products

Featured Support Topics

Kein Inhalt gefunden

Seiten