From: Moritz Schlarb (schlarbm_at_uni-mainz.de)
Date: Fri Jan 06 2012 - 09:29:18 CST
I'm currently working on deploying NAMD to the linux cluster at the
Johannes Gutenberg university Mainz, Germany.
I successfully compiled NAMD with the MVAPICH2 MPI and now I wanted to
compare its speed to a version of NAMD using ibverbs.
I compiled charm++ using the following commandline:
$ ./build charm++ net-linux-x86_64 ibverbs --no-build-shared
and running the megatest works (nodelist with two nodes):
$ ./charmrun ++remote-shell ssh +p2 ./pgm
test 53: completed (5.47 sec)
All tests completed, exiting
Then I configure namd with the following line:
$ ./config Linux-x86_64-g++ --charm-arch net-linux-x86_64-ibverbs
which compiles cleanly.
The resulting namd2 executable works fine when I run it locally:
$ ./namd2 src/alanin
WallClock: 0.035015 CPUTime: 0.010000 Memory: 31.363281 MB
$ charmrun ++local +p2 namd2 src/alanin
WallClock: 1.304384 CPUTime: 1.270000 Memory: 70.000000 MB
But when I want to run it on remote nodes (using the same nodelist as
above), I get a timeout:
$ ./charmrun ++remote-shell ssh +p2 ++verbose namd2 src/alanin
Charmrun> Waiting for 0-th client to connect.
Charmrun> error 0 attaching to node:
Timeout waiting for node-program to connect
When I look at an htop on the remote node, I see some shells spawning
According to this answer from the mailing list, I already tried using
++useip and ++usehostname in the charmrun commandline and specified the
infiniband ip addresses in the nodelist, but neither of that worked.
I've attached the complete run log and uploaded the tarred namd
directories (namd_full.tgz is the whole NAMD_2.8._Source dir, namd.tgz
is only the Linux-x86_64-g++ dir) here:
Thanks in advance,
-- Moritz Schlarb High Performance Computing University Mainz, Germany
This archive was generated by hypermail 2.1.6 : Tue Dec 31 2013 - 23:21:32 CST