PC GAMESS/Firefly-related discussion club



Learn how to ask questions correctly


Re^5: Running Firefly (OpenMPI) with more than 256 CPUS.

Alex Granovsky
gran@classic.chem.msu.su


Hi,

Was this information obtained on the head node or on a regular node?

regards,
Alex

On Mon Jul 6 '09 6:43pm, Pasquale Morvillo wrote
------------------------------------------------
>Hi,

>>what is the output of "ulimit -a" command on the nodes you are using?

>core file size          (blocks, -c) unlimited
>data seg size           (kbytes, -d) unlimited
>scheduling priority             (-e) 0
>file size               (blocks, -f) unlimited
>pending signals                 (-i) 270336
>max locked memory       (kbytes, -l) unlimited
>max memory size         (kbytes, -m) unlimited
>open files                      (-n) 4096
>pipe size            (512 bytes, -p) 8
>POSIX message queues     (bytes, -q) 819200
>real-time priority              (-r) 0
>stack size              (kbytes, -s) unlimited
>cpu time               (seconds, -t) unlimited
>max user processes              (-u) 270336
>virtual memory          (kbytes, -v) unlimited
>file locks                      (-x) unlimited

>>Working in standard mode, P2P uses two sockets per each peer,
>>while in XDLB mode, there are four sockets per each peer.

>>Thus, if you run Firefly in parallel on 256 nodes, each Firefly's instance will need either 512 or 1024 open sockets (file descriptors).

>>The typical default limit on most Linux installation is 1024 open file descriptors per user.
>>You may need to check the system-wide limit as well.
>

>

[ This message was edited on Mon Jul 6 '09 at 7:54pm by the author ]


[ Previous ] [ Next ] [ Index ]           Mon Jul 6 '09 7:54pm
[ Reply ] [ Edit ] [ Delete ]           This message read 1095 times