[GE users] tight integration with mvapich and openmpi

Mike Hanby mhanby at uab.edu
Tue Oct 21 15:49:03 BST 2008


by default, slots == cores, however you can override this and define
however many slots you want for a node(s).

-----Original Message-----
From: Joseph Hargitai [mailto:joseph.hargitai at nyu.edu] 
Sent: Tuesday, October 21, 2008 9:33 AM
To: users at gridengine.sunsource.net
Subject: Re: [GE users] tight integration with mvapich and openmpi


what is slot referring to in this case? cores or nodes?  i can run on
two nodes with 8 cores each with this pe. According to what you say, i
should not be. Maybe i am misunderstanding something. 

(we are aware of the patch in the tight integration tar file - our
mvapich however is 1x not 0.9 so do not know how applicable it is.)  

b, we are not testing over ethernet. 

j

----- Original Message -----
From: Reuti <reuti at staff.uni-marburg.de>
Date: Tuesday, October 21, 2008 8:46 am
Subject: Re: [GE users] tight integration with mvapich and openmpi

> > pe_name           mvapich-8
> > slots             16
> 
> With allocation rule 8 this means a max. of 2 jobs. Is this intented?
> 
> > user_lists        NONE
> > xuser_lists       NONE
> > start_proc_args   /opt/gridengine/mpi/startmpi.sh -catch_rsh  
> > $pe_hostfile
> > stop_proc_args    /opt/gridengine/mpi/stopmpi.sh
> > allocation_rule   8
> > control_slaves    TRUE
> > job_is_first_task FALSE
> > urgency_slots     min


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list