dapl

Using Multiple DAPL* Providers with the Intel® MPI Library

Introduction

If your MPI program sends messages of drastically different sizes (for example, some 16 byte messages, and some 4 megabyte messages), you want optimum performance at all message sizes.  This cannot easily be obtained with a single DAPL* provider.  This is due to latency being a major factor for smaller messages, but bandwidth being more important for larger messages, and providers often making a tradeoff to improve one or the other.  The Intel® MPI Library, as of Version 4.1 Update 1, now supports up to three providers for a single rank of your job.

  • Разработчики
  • Linux*
  • Сервер
  • Продвинутый
  • Intel® MPI Library
  • Интерфейс проверки сообщений
  • dapl
  • Кластерные вычисления
  • Intel® Many Integrated Core Architecture
  • Using Two DAPL Providers for MPI on Xeon Phi™

    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 Library when running on a Xeon Phi™ coprocessor.  You can now choose two DAPL providers to use for a single job.

  • Разработчики
  • Linux*
  • Продвинутый
  • Intel® MPI Library
  • dapl
  • Интерфейс проверки сообщений
  • Intel® Many Integrated Core Architecture
  • Подписаться на dapl