Service:storage: Difference between revisions

From OACISS Systems Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
== Main storage: /home/users ==
== Main storage: /home/users ==


Most systems access NAS on [[Infrastructure:mnemosyne | Mnemosyne]]. This is the primary storage engine utilizing 14x12TB Seagate Exos disks in RAID-6. It has 135TB of disk available in a single large volume.
Most systems access NAS on [[Infrastructure:mnemosyne | Mnemosyne]]. This is the primary storage engine utilizing 14x12TB Seagate Exos disks in mdadm RAID-6. It has 135TB of disk available in a single large volume.


Mnemosyne has 512GB of memory for caching and can sustain up to 700MBps sequential write and ~3GBps sequential read.
Mnemosyne has 512GB of memory for caching and can sustain up to 700MBps sequential write and ~3GBps sequential read.
Line 38: Line 38:
* 12 x 18T disks forming a 150TB volume in RaidZ2
* 12 x 18T disks forming a 150TB volume in RaidZ2


BeeGFS itself has been assigned a directory on the warpspeed filesystem for its own metadata.
BeeGFS itself has been temporarily assigned a directory on the warpspeed filesystem (nvme mdadm raid1) for its own metadata.
 
Preliminary benchmark results using fio (posixaio, size=4G, end_fsync=1, iodepth=16, 60sec results) are below. 1M = 2^20.
 
* Large block (1M) sequential read
** 1 thread: 1520MBps
** 2 threads: 2260MBps
** 4 threads: 4835MBps
** 8 threads: 9017MBps
* Large block random read
** 1 thread: 1020MBps
** 2 threads: 2020MBps
** 4 threads: 3790MBps
* Medium block (64K) sequential read
** 1 thread: 1220MBps
** 2 threads: 2141MBps
** 4 threads: 4508MBps
* Medium block random read
** 1 thread: 370MBps
** 2 threads: 883MBps
** 4 threads: 1735MBps
* Small block (4K) sequential read
** 1 thread:
** 2 threads:
** 4 threads:
* Small block random read
** 1 thread: 42MBps
** 2 threads:
** 4 threads:
 
* Large block 75R/25W mixed IO:
** 1 thread:
** 2 threads:
** 4 threads:
* Medium block 75R/25W mixed IO:
** 1 thread: 449/151MBps
** 2 threads:
** 4 threads:
* Small block 75R/25W mixed IO:
** 1 thread:
** 2 threads:
** 4 threads:
 


== Upstairs storage ==
== Upstairs storage ==

Revision as of 06:23, 16 May 2022


OACISS has multiple network attached storage systems for user operations. In addition, certain systems may have additional local disks, most often for storage of local images related to container infrastructure like Docker or Shifter.

Network attached storage operates over the 172.17 Ethernet, which is increasingly being upgraded to 100GbE performance.

Main storage: /home/users

Most systems access NAS on Mnemosyne. This is the primary storage engine utilizing 14x12TB Seagate Exos disks in mdadm RAID-6. It has 135TB of disk available in a single large volume.

Mnemosyne has 512GB of memory for caching and can sustain up to 700MBps sequential write and ~3GBps sequential read.

Package tree: /packages

Package trees for RH7, RH8 and ppc64le are stored on two 4TB SAS-12G SSDs in RAID-1.

As packages are subject to almost exclusively read access, they are mounted synchronously.

The SSDs provide 1.2GBps sequential speed.

High performance storage: /gpfs/gpfs0

OACISS has deployed an IBM GS4S high-performance file server utilizing the Spectrum Scale storage engine. The ESS server cluster has 96 4TB SSDs providing a total of 250TB of storage. The ESS cluster is linked to the private storage network with 200Gbps of Ethernet bandwidth.

The underlying high-performance Spectrum Scale filesystem driver is able to deliver up to approximately 3GBps of sequential IO per thread.

High performance scratch: /storage/warpspeed

Mnemosyne hosts a low-latency 8TB scratch volume made from two 4TB Sabrent Rocket M.2 NVME SSDs configured in RAID-0.

BeeGFS storage

Experimental deployment of a BeeGFS high-performance NFS is underway.

The backing store is a ZFS pool to which are assigned:

  • 2 mirrored 4T NVME drives for ZFS metadata
  • 2 4T NVMEs assigned as cache
  • 12 x 18T disks forming a 150TB volume in RaidZ2

BeeGFS itself has been temporarily assigned a directory on the warpspeed filesystem (nvme mdadm raid1) for its own metadata.

Preliminary benchmark results using fio (posixaio, size=4G, end_fsync=1, iodepth=16, 60sec results) are below. 1M = 2^20.

  • Large block (1M) sequential read
    • 1 thread: 1520MBps
    • 2 threads: 2260MBps
    • 4 threads: 4835MBps
    • 8 threads: 9017MBps
  • Large block random read
    • 1 thread: 1020MBps
    • 2 threads: 2020MBps
    • 4 threads: 3790MBps
  • Medium block (64K) sequential read
    • 1 thread: 1220MBps
    • 2 threads: 2141MBps
    • 4 threads: 4508MBps
  • Medium block random read
    • 1 thread: 370MBps
    • 2 threads: 883MBps
    • 4 threads: 1735MBps
  • Small block (4K) sequential read
    • 1 thread:
    • 2 threads:
    • 4 threads:
  • Small block random read
    • 1 thread: 42MBps
    • 2 threads:
    • 4 threads:
  • Large block 75R/25W mixed IO:
    • 1 thread:
    • 2 threads:
    • 4 threads:
  • Medium block 75R/25W mixed IO:
    • 1 thread: 449/151MBps
    • 2 threads:
    • 4 threads:
  • Small block 75R/25W mixed IO:
    • 1 thread:
    • 2 threads:
    • 4 threads:


Upstairs storage

Cerberus, Chymera, and the nuc + jetson cluster have access to a smaller 22TB NAS, accessed over 1Gbit ethernet, located on Cerberus.

This storage, and package tree, is entirely separate from main storage.