[ExM Users] turbine engine and n

[Tim Armstrong]

Unfortunately in that case I think you have to sacrifice all the cores on a
node to run an ADLB server on one of them.

I think this is actually a difficult problem to solve with the way
OpenMP/MPI is usually done with one MPI communication context per process,
since ADLB server can't easily share them.

- Tim


On Mon, Apr 14, 2014 at 10:25 AM, Ketan Maheshwari <ketan at mcs.anl.gov>wrote:

> What if the application tasks are openmp as is the case with my current
> runs. They need to run as one process per node.
>
>
> On Mon, Apr 14, 2014 at 10:22 AM, Wozniak, Justin M. <wozniak at mcs.anl.gov>wrote:
>
>>  Hi
>>     You can set the environment variable PPN (processes-per-node) to
>> change this behavior.  PPN defaults to 1.
>>     Justin
>>
>>
>> On 04/14/2014 10:18 AM, Ketan Maheshwari wrote:
>>
>> Hi,
>>
>>  From my recent runs on ALCF systems, it looks like the n parameter
>> corresponds to the number of compute nodes. So, n = 3 will start a Turbine
>> engine, an ADLB server and a worker. However, it starts a three node job
>> and I was wondering if Turbine engine and ADLB server needs a full node as
>> opposed to a core to run.
>>
>>  Thanks,
>> Ketan
>>
>>
>> _______________________________________________
>> ExM-user mailing listExM-user at lists.mcs.anl.govhttps://lists.mcs.anl.gov/mailman/listinfo/exm-user
>>
>>
>>
>> --
>> Justin M Wozniak
>>
>>
>>
>
> _______________________________________________
> ExM-user mailing list
> ExM-user at lists.mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/exm-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/exm-user/attachments/20140414/7818a712/attachment.html>