Thanks, Gilles
On Sun, May 24, 2015 at 7:41 PM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:
> yes, that is clearly suboptimal.
>
> the optimal option is something like -bind-to hwthreads
> (I am afk so I cannot confirm this)
>
> Cheers,
>
> Gilles
>
> On Sunday, May 24, 2015,
yes, that is clearly suboptimal.
the optimal option is something like -bind-to hwthreads
(I am afk so I cannot confirm this)
Cheers,
Gilles
On Sunday, May 24, 2015, XingFENG wrote:
> Hi, Gilles,
>
> Thanks very much for your respond. But if I oversubscribe, would
Hi, Gilles,
Thanks very much for your respond. But if I oversubscribe, would the
performance be influenced?
On Sun, May 24, 2015 at 7:24 PM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:
> Hi Xing,
>
> iirc, open MPI default behavior is to bind to cores (vs hyperthreads),
> hence
Hi Xing,
iirc, open MPI default behavior is to bind to cores (vs hyperthreads),
hence the error message.
I cannot remember the option to bind to threads, but you can mpirun
--oversubscribe if you are currently stuck
Cheers,
Gilles
On Sunday, May 24, 2015, XingFENG
Hi, OPENMPI users,
I have met some problem while doing experiments on Amazon EC2. I have
chosen instance type r3.2xlarge. As amazon claimed, it has 8 vcpu. Each
vCPU is a hyperthread of an Intel Xeon core for M3, C4, C3, R3, HS1, G2,
I2, and D2. (from *https://aws.amazon.com/ec2/instance-types/