More local disks updates

Author: rkdarst

triton/ref/slurm.rst

@@ -32,6 +32,7 @@
                             ! ``--exclusive``                ! allocate exclusive access to nodes.  For large parallel jobs.
                             ! ``--constraint=``\ *FEATURE*   ! request *feature* (see ``slurm features`` for the current list of configured features, or Arch under the :ref:`hardware list <hardware-list>`).  Multiple with ``--constraint="hsw|skl"``.
                             ! ``--constraint=localdisk``     ! request nodes that have local disks
+			    ! ``--tmp=nnnG``                 ! Request ``nnn`` GB of :doc:`local disk storage space </triton/usage/localstorage>`
                             ! ``--array=``\ *0-5,7,10-15*    ! Run job multiple times, use variable ``$SLURM_ARRAY_TASK_ID`` to adjust parameters.
                             ! ``--gres=gpu``                 ! request a GPU, or ``--gres=gpu:``\ *n* for multiple
                             ! ``--mail-type=``\ *TYPE*       ! notify of events: ``BEGIN``, ``END``, ``FAIL``, ``ALL``, ``REQUEUE`` (not on triton) or ``ALL.`` MUST BE used with ``--mail-user=`` only

triton/ref/storage.rst

@@ -6,5 +6,5 @@
    Home                            | ``$HOME`` or ``/home/USERNAME/``           | hard quota 10GB             | Nightly   | all nodes                      | Small user specific files, no calculation data.
    Work                            | ``$WRKDIR`` or ``/scratch/work/USERNAME/`` | 200GB and 1 million files   | x         | all nodes                      | Personal working space for every user. Calculation data etc. Quota can be increased on request.
    Scratch                         | ``/scratch/DEPT/PROJECT/``                 | on request                  | x         | all nodes                      | Department/group specific project directories.
-   Local temp                      | ``/tmp/`` (nodes with disks only)          | local disk size             | x         | single-node                    | (Usually fastest) place for single-node calculation data.  Removed once user's jobs are finished on the node.  Request with ``--constraint=localdisk``.
-   ramfs                           | ``/dev/shm/`` (and ``/tmp/`` on diskless nodes) | limited by memory      | x         | single-node                    | Very fast but small in-memory filesystem
+   :doc:`Local temp (disk) </triton/usage/localstorage>` | ``/tmp/`` (nodes with disks only)          | local disk size             | x         | single-node                    | (Usually fastest) place for single-node calculation data.  Removed once user's jobs are finished on the node.  Request with ``--tmp=nnnG`` or ``--constraint=localdisk``.
+   :doc:`Local temp (ramfs) </triton/usage/localstorage>`       | ``/dev/shm/`` (and ``/tmp/`` on diskless nodes) | limited by memory      | x         | single-node                    | Very fast but small in-memory filesystem

triton/tut/storage.rst

@@ -152,11 +152,9 @@ Local disks
 with single-node jobs and is cleaned up after job is finished.  Not
 all nodes have them: some don't have any disks, and ``/tmp`` is also
 in-memory ramfs.  If you want to ensure you have local storage,
-submit your job with ``--constraint=localdisk``.
+submit your job with ``--constraint=localdisk`` and/or ``--tmp=nnnG``.
 
-See the :doc:`Compute
-node local drives <../usage/localstorage>` page for further details and script
-examples.
+See :doc:`../usage/localstorage`
 
 .. _ramfs-description:
 
@@ -170,7 +168,11 @@ temporary files that don't need to last long.  Note that this is no
 different than just holding the data in memory, if you can hold in
 memory that's better.
 
-ramfs counts against the memory of your job or user session.
+ramfs counts against the memory of your job or user session, so your
+``--mem`` value must be increased based on your storage space.
+
+See :doc:`../usage/localstorage` (which also covers ramfs).
+
 
 Other Aalto data storage locations
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

triton/usage/localstorage.rst

@@ -61,7 +61,7 @@ double check from within the cluster, you can verify node info with
 tens of TB.
 
 You have to use ``--constraint=localdisk`` to ensure that you get a
-hard disk.  You can use ``--tmp=NNNG`` (for example ``--tmp=100G``) to
+hard disk.  You can use ``--tmp=nnnG`` (for example ``--tmp=100G``) to
 request a node with at least that much temporary space.  But,
 ``--tmp`` doesn't allocate this space just for you: it's shared among
 all users, including those which didn't request storage space.  So,