Performance

​

Performance Overview

Regatta file systems are designed to provide enterprise-grade performance while syncronizing with data sets in S3.

​

Caching

Regatta intelligently caches data to maximize the performance of your file system. If your application requests data that’s not in the cache, Regatta will fetch the data from the backing bucket and then cache it for future requests. Regatta keeps this data in cache for up to 1 hour after the final read or write operation to the data. Regatta may cache up to 10 MiB of additional data from the backing bucket than requested.

​

Latency

Regatta file systems are designed to provide consistent, sub-millisecond time-to-first-byte latencies for all cached read and write operations. Uncached read latencies depend on the specific backing storage provider. For example, for Amazon S3, uncached reads are typically in the 10-30ms range.

​

Scalability

By default, Regatta file systems can provide up to 10 Gbps of throughput and 10,000 IOPS across all connected clients.