User Ramdisk

Using Ramdisk

On the GPC nodes, a `ramdisk' is available. Up to 70 percent of the ram on the node (i.e. 11GB on most nodes) may be used as a temporary file system. This is particularly useful for use in the early stages of migrating desktop-computing codes to a High Performance Computing platform such as the GPC, especially those that use a lot of I/O, such as Blast. Using a lot if I/O becomes a bottleneck in large scale computing. One especially suffers a performance penalty on parallel file systems (such as the GPFS used on SciNet), since the files are synchronized across the whole network.

Ramdisk is much faster than real disk, and is especially beneficial for codes which perform a lot of small I/O work, since the ramdisk does not require network traffic.

However, each node sees its own ramdisk and cannot see files on that of other nodes. You can also not see the ramdisks of the compute nodes on the devel nodes. To track progress on a ramdisk, you'd have to ssh into the respective compute node.

To use the ramdisk, create and read to or write from files in /dev/shm/ just as one would to (e.g.) $SCRATCH. Only the amount of RAM needed to store the files will be taken up by the temporary file system. Thus if you have 8 serial jobs each requiring 1 GB of RAM, and 2GB is taken up by various OS services, you would still have approximately 6GB available to use as ramdisk on a 16GB node. However, if you were to write 7 GB of data to the RAM disk, this would exceed available memory and your job would crash.

Note that when using the ramdisk:

At the start of your job, you can copy frequently accessed files to ramdisk (stage in). If there are many such files, it is beneficial to put them in a tar file.
One would periodically copy the output files from ramdisk to /scratch or /project, as well as at the end of the job, of course (stage out).
It is very important to delete your files from ram disk at the end of your job. If you do not do this, the next user to use that node will have less RAM available than they might expect, and this might kill their jobs.

A simple script using the ramdisk for 8 serial jobs in a 4 hour window might look like this: <source lang="bash">

!/bin/bash
MOAB/Torque submission script for SciNet GPC
PBS -l nodes=1:ppn=8,walltime=4:00:00
PBS -N ramdisk-example

mkdir /dev/shm/workdir cp $PBS_O_WORKDIR/* /dev/shm/workdir cd /dev/shm/workdir for ((i=1;i<=8;i++)); do

 ./executable < $i.in > $i.out &

done wait tar cf $PBS_O_WORKDIR/out.tar ?.out </source>

A more complex example

A more complete script using the ramdisk in a 1 day openMP job that saves output periodically, might look like this: <source lang="bash">

!/bin/bash
MOAB/Torque submission script for SciNet GPC
PBS -l nodes=1:ppn=8,walltime=24:00:00
PBS -N ramdisk-test

Job parameters:

execname=job # name of the executable input_tar=input.tar # tar file with input files and executables output_tar=out.tar # file in which to store output input_subdir=indir # sub-directory (within input_tar) with input files output_subdir=outdir # sub-directory to contain of output files poll_period=60 # how often check for job completion (in seconds) save_period=120 # how often to save output (in minutes)

Track how long everything takes.

date

Copy to ramdisk

echo "Stage-in: copying files to ramdisk directory /dev/shm/$USER" mkdir -p /dev/shm/$USER mkdir -p /dev/shm/$USER/$output_subdir cd /dev/shm/$USER cp $PBS_O_WORKDIR/$input_tar . tar xf $input_tar rm -rf $input_tar

Track how long everything takes.

echo -n "Stage-in completed on " date

Run on ramdisk

echo "Starting job" ./$execname $input_subdir $output_subdir &

Store the process id in $pid so we may check if it's still running:

pid=$!

Note:
1. The above launching command is appropriate for a multi-threaded (openMP) applications.
2. Ramdisk MPI jobs are limited to 1 node as /dev/shm is not shared across nodes.
3. For serial jobs, you'd want to start 8 jobs at the same time instead, e.g.
mkdir -p $output_subdir/1
./$execname ${input_subdir}/1 ${output_subdir}/1 &
pid=$!
mkdir -p $output_subdir/2
./$execname ${input_subdir}/2 ${output_subdir}/2 &
pid=$pid,$!
mkdir -p $output_subdir/3
./$execname ${input_subdir}/3 ${output_subdir}/3 &
pid=$pid,$!
mkdir -p $output_subdir/4
./$execname ${input_subdir}/4 ${output_subdir}/4 &
pid=$pid,$!
mkdir -p $output_subdir/5
./$execname ${input_subdir}/5 ${output_subdir}/5 &
pid=$pid,$!
mkdir -p $output_subdir/6
./$execname ${input_subdir}/6 ${output_subdir}/6 &
pid=$pid,$!
mkdir -p $output_subdir/7
./$execname ${input_subdir}/7 ${output_subdir}/7 &
pid=$pid,$!
mkdir -p $output_subdir/8
./$execname ${input_subdir}/8 ${output_subdir}/8 &
pid=$pid,$!

Track how long everything takes.

echo -n "Job started on " date

function save_results {

   echo -n "Copying from directory $output_subdir to file $PBS_O_WORKDIR/$output_tar on "
   date
   tar cf $output_tar $output_subdir/*
   cp $output_tar $PBS_O_WORKDIR
   echo -n "Copying of output complete on "
   date

}

function cleanup_ramdisk {

   echo -n "Cleaning up ramdisk directory /dev/shm/$USER on "
   date
   rm -rf /dev/shm/$USER
   echo -n "done at "
   date

}

function trap_term {

   echo -n "Trapped term (soft kill) signal on "
   date
   save_results
   cleanup_ramdisk
   exit

}

function interruptible_sleep {

   # waits for a number of seconds
   # argument 1 = number of seconds
   # note: just doing `sleep $1' would not be interruptible!
   for m in `seq $1`; do  
       sleep 1
   done

}

function is_running {

   # check if one or more process is running 
   # argument 1 = a command separated list of PIDs (no spaces)
   ps -p $1 -o pid= | wc -l

}

trap the termination signal, and call the function 'trap_term' when
that happens, so results may be saved.

trap "trap_term" TERM

number of pollings per save period (rounded down):

npoll=$(($save_period*60/$poll_period))

polling and saving loop

running=$(is_running $pid) while [ $running -gt 0 ] do

   for n in `seq $npoll`
   do
       interruptible_sleep $poll_period
       running=$(is_running $pid)
       if [ $running -eq 0 ]; then
           break
       fi
   done
   save_results

done

Done

cleanup_ramdisk

echo -n "Job finished cleanly on " date

</source> Notes with this script:

The script assumes that the tar file input.tar contains the executable job and the input files in a subdirectory called indir (with further subdirectories for the case of 8 serial jobs).
The executable is supposed to take the locations of the input and output directory as arguments.
The trap comment makes sure that the results gets saved and the ramdisk gets flushed even when the jobs gets killed before the end of the script is reached. trap is a bash script construction that executes the given command when the script is given, in this case, a TERM signal. The TERM signal is given by the scheduler 30 seconds before your time is up.
You could also trap signals in your C, C++ or FORTRAN codes.
All files are kept in a subdirectory of /dev/shm. This makes the clean up simpler, and keeps things tidy when doing small test jobs on the development nodes.

Further notes:

Often collections of serial jobs are run on the ramdisk, see the serial run wiki page for more details on that.
If your application needs just a bit more ramdisk, there are 24 nodes with 18GB and 84 nodes with 32GB of RAM. These nodes can be requested by qsub -l nodes=2:m18g:ppn=8,walltime=1:00:00 or qsub -l nodes=2:m32g:ppn=8,walltime=1:00:00. They are infiniband nodes, which are in short supply, so only use these nodes if you have to. Finally, there are 2 stand-alone large memory (128GB) nodes. They have 16 cores and are intel machines running linux, but they are not the same architecture (Nehalem) as the GPC compute nodes, so codes may have to be compiled separately for these machines. They can be accessed using a specific largemem queue. See GPC Quickstart.

--Rzon 18 June 2010 (UTC)

User Ramdisk

Using Ramdisk

A more complex example

Navigation menu

Search