thanks for clarifying there is only one container per host.
do you always run 16 tasks per host/container ?
or do you always run 16 hosts/containers ?
also, do lxc sets iptables when you start a container ?
Cheers,
Gilles
On Tuesday, July 28, 2015, Cristian RUIZ wrote:
> Thank you for answe
Thank you for answering. I executed the test with the following command:
mpirun --mca btl self,sm,tcp --machinefile machine_file cg.B.128 in
both setups. My machine file is composed of 128 lines (each machine
hostname is repeated 16 times). There is just one container per machine
and the cont
Cristian,
one more thing...
make sure tasks run on the same physical node with and without containers.
for example, if in native mode, tasks 0 to 15 run on node 0, then in
container mode, tasks 0 to 15 should run on 16 containers hosted by node 0
Cheers,
Gilles
On Tuesday, July 28, 2015, Gilles
Cristian,
If the message takes some extra time to land into the receiver, then
MPI_Wait will take more time.
or even worse, if the sender is late, the receiver will spend even more
time in MPI_Wait.
First, how do you run 128 tasks on 16 nodes ?
if you do a simple mpirun, then you will use sm or v
Hello,
I'm measuring the overhead of using Linux container for HPC
applications. To do so I was comparing the execution time of NAS
parallel benchmarks on two infrastructures:
1) real: 16 real machines
2) container: 16 containers distributed over 16 real machines
Each machine used is equippe
