Warning

This documentation is for a pilot service. It is likely incomplete or may be inaccurate as the service is developed.

Although RCC is currently free-at-point-of-use projects are assigned budgets, therefore the documentation here will explain ways in which to make optimal use of the services provided.

Drive Storage

Drive storage, or ‘block storage’ as it’s sometimes more generally referred to as, is the storage attached directly to your instances within Ronin. The other main type of stored available in Ronin is Object Storage / S3. Drive/block storage offers better performance for both reading/writing data and also for file metadata queries, but object storage is cheaper and offers larger capacities.

These are most commonly the ‘Root Drive’ however Ronin gives you the option to create your own additional drive/block storage devices that can be attached to instances and moved _between_ instances.

Should you want to know about the nitty gritty, the underlying technology used here is AWS EBS.

Drive Types

When creating a new non-root drive, Ronin gives you multiple options for drive types. As a general rule of thumb we recommend you select SSD, this is due to how AWS provisions drive speed.

The SSD drives will be allocated * 125 MiB/s of read and write performance and * 3000 of IOPS (‘input/output operations per second’) (as per gp3 defaults). Should your workload require more performance please do get in touch.

For those wondering why we omit the other drive options, this is mainly due to the behavior of the magnetic storage classes. The HDD storage classes base their throughput off the provisioned storage size see here. Because of this we recommend that you use Object Storage / S3 for storing large amounts of data.