<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hi David, in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959939#M3158</link>
    <description>&lt;P&gt;Hi David,&lt;/P&gt;
&lt;P&gt;I misunderstood your original question, so let's change approach.&amp;nbsp; We do not currently check resource utilization from the job manager.&amp;nbsp; Internally, we typically reserve an entire node for a single job when running, as two different MPI jobs do not communicate with each other.&lt;/P&gt;
&lt;P&gt;At present, the only way to do this is manually.&amp;nbsp; You'll need to get a list of available cores from SLURM*.&amp;nbsp; Is your application single or multi-threaded?&lt;/P&gt;
&lt;P&gt;If single threaded, then you'll set I_MPI_PIN_PROCESSOR_LIST to match the available (and desired) cores, with one rank going to each core.&amp;nbsp; This will define a single core for each rank to use.&lt;/P&gt;
&lt;P&gt;If multi-threaded, then you'll set I_MPI_PIN_DOMAIN instead.&amp;nbsp; This will set a group of cores available for each rank, and you'll use KMP_AFFINITY to control the thread placement within that domain.&lt;/P&gt;
&lt;P&gt;There are quite a few syntax options for each of these variables, so please check the &lt;A href="http://software.intel.com/sites/products/documentation/hpc/ics/impi/41/lin/Reference_Manual/index.htm"&gt;Reference Manual&lt;/A&gt; for full details.&lt;/P&gt;
&lt;P&gt;As Tim said, if you're interested, I can file a feature request for this capability.&lt;/P&gt;
&lt;P&gt;Sincerely,&lt;BR /&gt; James Tullos&lt;BR /&gt; Technical Consulting Engineer&lt;BR /&gt; Intel® Cluster Tools&lt;/P&gt;</description>
    <pubDate>Tue, 14 May 2013 19:07:27 GMT</pubDate>
    <dc:creator>James_T_Intel</dc:creator>
    <dc:date>2013-05-14T19:07:27Z</dc:date>
    <item>
      <title>Multiple IntelMPI Jobs On A Single Node using Slurm</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959935#M3154</link>
      <description>&lt;P&gt;I have a cluster single node of 4 socket total 32 corers. The systems running Redhat 6.3, and intelmpi 4 update 3. I am using Slurm to start mpi jobs.&amp;nbsp;It seems that whenever I try to run multiple MPI jobs to a single node all the jobs end up running on the same processors. Moreover i notice that the job use all the cores in the node. For example: i started with the first mpi job using Slurm on the node with 8 cores; and i notice that the first mpi task run on 0 to 3 cpus, the2-ndmpi task on 4-7 cpus, and so on the last task on 28-31. Each mpi task used 4 cores instead 1. i started the 2-nd job with 8 cores, and i notice the same and they run on the same 32 cpus of the first job.&lt;/P&gt;
&lt;P&gt;there a way to tell mpirun using Slurm to set the taskset affinity correctly at each run so that it will choose only the idle processors according the Slurm?&lt;BR /&gt; Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2013 09:18:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959935#M3154</guid>
      <dc:creator>David_Touati</dc:creator>
      <dc:date>2013-05-14T09:18:14Z</dc:date>
    </item>
    <item>
      <title>As far as I know, you must</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959936#M3155</link>
      <description>&lt;P&gt;As far as I know, you must set I_MPI_PIN_DOMAIN=off in order for this to work at all.&amp;nbsp; If you can demonstrate value for receiving CPU assignments from slurm, you might file a feature request.&amp;nbsp;&amp;nbsp; I don't thnk spllitting it down to the core level for separate jobs is likely to work well.&amp;nbsp; Maybe splitting down to socket level could be useful.&amp;nbsp; You could make a case that clusters with nodes of 4 or more CPUs will be more valuable with such a feature.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If your request turns out to be out of the main stream, you might have to script it yourself, using KMP_AFFINITY or the OpenMP 4.0 equivalent to assign cores to each job.&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2013 13:32:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959936#M3155</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2013-05-14T13:32:47Z</dc:date>
    </item>
    <item>
      <title>Hi David,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959937#M3156</link>
      <description>&lt;P&gt;Hi David,&lt;/P&gt;
&lt;P&gt;If you are using cpuset, the current version of the Intel® MPI Library does not support it.&amp;nbsp; The next release will, so if that is the case, just sit tight for a bit longer.&lt;/P&gt;
&lt;P&gt;If not, let me know and we'll work from there.&lt;/P&gt;
&lt;P&gt;Sincerely,&lt;BR /&gt; James Tullos&lt;BR /&gt; Technical Consulting Engineer&lt;BR /&gt; Intel® Cluster Tools&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2013 14:01:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959937#M3156</guid>
      <dc:creator>James_T_Intel</dc:creator>
      <dc:date>2013-05-14T14:01:45Z</dc:date>
    </item>
    <item>
      <title>Thanks james,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959938#M3157</link>
      <description>&lt;P&gt;Thanks james,&lt;/P&gt;
&lt;P&gt;I am not using cpuset. I assume that slume that will do the work.&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2013 17:10:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959938#M3157</guid>
      <dc:creator>David_Touati</dc:creator>
      <dc:date>2013-05-14T17:10:09Z</dc:date>
    </item>
    <item>
      <title>Hi David,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959939#M3158</link>
      <description>&lt;P&gt;Hi David,&lt;/P&gt;
&lt;P&gt;I misunderstood your original question, so let's change approach.&amp;nbsp; We do not currently check resource utilization from the job manager.&amp;nbsp; Internally, we typically reserve an entire node for a single job when running, as two different MPI jobs do not communicate with each other.&lt;/P&gt;
&lt;P&gt;At present, the only way to do this is manually.&amp;nbsp; You'll need to get a list of available cores from SLURM*.&amp;nbsp; Is your application single or multi-threaded?&lt;/P&gt;
&lt;P&gt;If single threaded, then you'll set I_MPI_PIN_PROCESSOR_LIST to match the available (and desired) cores, with one rank going to each core.&amp;nbsp; This will define a single core for each rank to use.&lt;/P&gt;
&lt;P&gt;If multi-threaded, then you'll set I_MPI_PIN_DOMAIN instead.&amp;nbsp; This will set a group of cores available for each rank, and you'll use KMP_AFFINITY to control the thread placement within that domain.&lt;/P&gt;
&lt;P&gt;There are quite a few syntax options for each of these variables, so please check the &lt;A href="http://software.intel.com/sites/products/documentation/hpc/ics/impi/41/lin/Reference_Manual/index.htm"&gt;Reference Manual&lt;/A&gt; for full details.&lt;/P&gt;
&lt;P&gt;As Tim said, if you're interested, I can file a feature request for this capability.&lt;/P&gt;
&lt;P&gt;Sincerely,&lt;BR /&gt; James Tullos&lt;BR /&gt; Technical Consulting Engineer&lt;BR /&gt; Intel® Cluster Tools&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2013 19:07:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Multiple-IntelMPI-Jobs-On-A-Single-Node-using-Slurm/m-p/959939#M3158</guid>
      <dc:creator>James_T_Intel</dc:creator>
      <dc:date>2013-05-14T19:07:27Z</dc:date>
    </item>
  </channel>
</rss>

