NCAR machines (bluefire and bluevista)


Note: blueice has been decommissioned and bluefire was delivered instead (2008/06-).

This page describes G-RSM on bluevista and bluefire. We do not currently use lightning and blueice.

There is a report that pserver now works on NCAR machines. Please try
setenv CVSROOT :pserver:anoncvs@rokka.ucsd.edu:/rokka1/kana/cvs-server-root/cpscvs
before trying below.

If you have an account on rokka, you can download the model directly from rokka through CVS.
In order to access the CVS server at ECPC, add these lines to your .cshrc
setenv CVSROOT :ext:Your NCAR User ID@rokka.ucsd.edu:/rokka1/kana/cvs-server-root/cpscvs
setenv CVS_RSH ssh

Please note that you need to contact model master (e.g. kana@ucsd.edu) to set up your account on rokka. Also note taht this can be arranged only on special circumstances. If this is not possible, please follow the instruction below.

All others have to download the model on a machine elsewhere and transfer the package to blueice/bluevista. It may be useful to use the following "install" script option that creates a tar package of the entire G-RSM code.
install –enable-tar

The current installer recognizes blueice as MACHINE=ibmspbl and bluevista as MACHINE=ibmspbv.

Please look at this page before setting a regional domain. There are some restrictions on the choice of igrd for use with FFT on IBM machines.

Bluefire

Bluefire inherits most of blueice, so the G-RSM runs with the same configuration as blueice (and bluevista). Choose "ibmspbv" for your machine. The speed became roughly doubled to blueice.

Blueice (decommissioned)

G-RSM runs on blueice just like on bluevista.

BENCHMARK TEST (RSM one-month run with rsim script)

real # of pes

Japan (288x309 grids)
California (288x349 grids)
blueice
128
128pes, 8x16-way nodes, no-SMT
13.4 hours


128
256pes, 8x16-way nodes, SMT
8.3 hours
9.4 hours

256
512pes, 16x16-way nodes, SMT
4.4 hours
5.4 hours
bluevista
64
128pes, 8x8-way nodes, SMT
14.2 hours
15.7 hours

128
256pes, 16x8-way nodes, SMT
7.5 hours
8.3 hours
lonestar (TACC)
128
128pes, 32x4-way nodes
9.0 hours

On both machines it is recommended to use SMT for this domain size. Bluevista is slightly faster than blueice. I have not done any optimization specifically for blueice so there may be some room for improvement on blueice. Blueice has much more processors than bluevista so I expect faster turnaround time on blueice. (Hideki)

Bluevista

Bluesky (DECOMMISSIONED)

Discussions

juliavm

RSM performance on Bluefire

juliavm 29 September 2008 14:25:46

I have recently installed RSM on Bluefire and configured with MACHINE=ibmspbv (bluevista). I have integrated it for the LBA domain for 1 month with NCEP reanalysis forcing using a number of NPES (32, 64, 128 with and without SMT). I am getting about the same performance in all cases (wallclock is about 1 hr). In fact, for NPES=128 and ptile=32 and 64 wallclock increases to 1hr 20min and 1hr 45min respectively.

Am I missing something?

Thank you for your help,

Julia

kei
kei 29 September 2008 22:45:12

Hi.

The scalability is largely affected to the number of x-y grids. I'm not so sure, but this might be a part of the reason.

Also, you should compare NPES=128/ptile=64 (with SMT) and NPES=64/ptile=32 (without SMT) for RSM, because SMT is "virtual double-core" function (i.e., in both cases, real nodes used are two). From your experiments, it was known that we should use SMT (ptile=64), because the GAU was much cheaper for the similar wall time. Wasn't this right?

By the way, according to the NCAR's information (see http://www.cisl.ucar.edu/cpg/dailyb/todays.html ; article on 09/24/08), there is a case that without-SMT is faster than with-SMT. But this is not the case for RSM.

Kei