cc_staff
290
edits
Data management at Niagara: Difference between revisions
→/archive
m (→/project) |
|||
| Line 24: | Line 24: | ||
=== /archive === | === /archive === | ||
/archive is a nearline storage pool, if you want to temporarily offload semi-active material from any of the above file systems. In practice users will offload/recall material as part of their regular workflow, or when they hit their quotas on scratch or project. That material can remain on HPSS for a few months to a few years. Note that on niagara /archive is only available to groups with RAC allocation. | /archive is a nearline storage pool, if you want to temporarily offload semi-active material from any of the above file systems. In practice users will offload/recall material as part of their regular workflow, or when they hit their quotas on scratch or project. That material can remain on HPSS for a few months to a few years. Note that on niagara /archive is only available to groups with RAC allocation. | ||
=== /dev/shm (RAM) === | |||
On the Niagara nodes a [[User_Ramdisk | ramdisk]] is available. [[User_Ramdisk | Ramdisk]] is much faster than real disk, and faster than Burst Buffer. Up to 70 percent of the RAM on the node (i.e. 202GB) may be used as a temporary '''local''' file system. This is particularly useful in the early stages of migrating desktop-computing codes to a HPC platform such as Niagara, especially those that use a lot of file I/O (Input/Output). Using a lot of I/O is a bottleneck in large scale computing, especially on parallel file systems (such as the GPFS used on Niagara), since the files are synchronized across the whole network. | |||
= Quotas and purging = | = Quotas and purging = | ||