On Mar 1, 2012, at 3:33 AM, Pinero, Pedro_jose wrote:
> I am launching 200 light processes in two computers with 8 cores each one
> (Intel i7 processor). They are dedicated and are interconnected through a
> point-to-point Gigabit Ethernet link.
>
> I read about oversubscribing nodes in the op
Wow - with that heavy an oversubscription, your performance experience
certainly is reasonable. Not much you can do about it except reduce the
oversubscription, either by increasing the number of computers or reducing the
number of processes.
On Mar 1, 2012, at 1:33 AM, Pinero, Pedro_jose wrot
Thank you for your fast response.
I am launching 200 light processes in two computers with 8 cores each
one (Intel i7 processor). They are dedicated and are interconnected
through a point-to-point Gigabit Ethernet link.
I read about oversubscribing nodes in the open-mpi documentation, and
f
two things:
1. Too many mpi processes on one node leading to processes pre-empting each
other
2. Contention in your network.
On Wed, Feb 29, 2012 at 8:01 AM, Pinero, Pedro_jose <
pedro_jose.pin...@atmel.com> wrote:
> Hi,
>
> ** **
>
> I am using OMPI v.1.5.5 to communicate 200 Processes in a
On Feb 29, 2012, at 11:01 AM, Pinero, Pedro_jose wrote:
> I am using OMPI v.1.5.5 to communicate 200 Processes in a 2-Computers cluster
> connected though Ethernet, obtaining a very poor performance.
Let me making sure I'm parsing this statement properly: are you launching 200
MPI processes on
Hi,
I am using OMPI v.1.5.5 to communicate 200 Processes in a 2-Computers
cluster connected though Ethernet, obtaining a very poor performance. I
have measured each operation time and I haver realised that the
MPI_Gather operation takes about 1 second in each synchronization (only
an integer is
