You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I measured the throughput of batches of 10_000 object read/write operations. First, the benchmarks begin approaching a throughput limit as the size of read/written segments increases, but at some point the throughput collapses and is greatly reduced from there on out. This occurs on my machine as well as on the OVGU ants cluster (ant14).
The limit itself is influenced by the I/O interface used. On the cluster, POSIX I/O approached a limit of around 6 GB, a mmap backend approached 3 GB. The collapse occurs between segment sizes of 256 and 512 KiB, regardless of the I/O interface.
POSIX sequential write (ant14 is ssd, hdd, nvme; local is local):
with linear scaling for dramatic effect:
The text was updated successfully, but these errors were encountered:
I measured the throughput of batches of 10_000 object read/write operations. First, the benchmarks begin approaching a throughput limit as the size of read/written segments increases, but at some point the throughput collapses and is greatly reduced from there on out. This occurs on my machine as well as on the OVGU ants cluster (ant14).
The limit itself is influenced by the I/O interface used. On the cluster, POSIX I/O approached a limit of around 6 GB, a mmap backend approached 3 GB. The collapse occurs between segment sizes of 256 and 512 KiB, regardless of the I/O interface.
POSIX sequential write (ant14 is ssd, hdd, nvme; local is local):
with linear scaling for dramatic effect:
The text was updated successfully, but these errors were encountered: