On Mon, Jan 11, 2021 at 05:25:56PM +, Josh Hursey via users wrote:
> Thank you for the bug report. I filed a bug against PRRTE so this doesn't get
> lost that you can follow below:
> https://github.com/openpmix/prrte/issues/720
>
> Making rankfle a per-job instead of a per-DVM option might
Hi, is there a way to allocate more resources to rank 0 than to
any of the other ranks in the context of PRRTE DVM?
With mpirun (aka. prte) launcher, I can successfully accomplish this
using a rankfile:
rank 0=+n0 slot=0
rank 1=+n1 slot=0
rank 2=+n1 slot=1
mpirun -n 3 --bind-to n
On Sat, Nov 14, 2020 at 08:07:47PM +, Ralph Castain via users wrote:
> IIRC, the correct syntax is:
>
> prun -host +e ...
>
> This tells PRRTE that you want empty nodes for this application. You can even
> specify how many empty nodes you want:
>
> prun -host +e:2 ...
>
> I haven't tested
Hi, in context of the PRRTE Distributed Virtual Machine, is there a way
to tell the task mapper inside prun to not share a node across separate
prun jobs?
For example, inside a resource allocation from Cobalt/ALPS: 2 nodes with
64 cores each:
prte --daemonize
prun ... &
...
prun ... &
pterm
Scen
