act

The Aerospike ACT benchmarking tool characterizes flash devices on their latency under a fixed read/write profile. It won't tell you how fast your device is, it will tell you if a workload runs under a certain latency bound. https://docs.aerospike.com/server/operations/plan/ssd/ssd_ce... https://github.com/aerospike/act If you set max-lag-sec: 0 Then it will continue to run even if temporarily falls behind.

It depends, yes but ... (not discounting any of the above). One sees a lot of 3:1 in practice due to the replication factor. If you have 3 copies of the data and the client can read from any node, you get 3x the read performance as having to have a quorum write on two out of three nodes. To the GP, for a rough swag of what is possible out of given hardware, a combination of FIO and ACT (measures IO latency under a fixed load) is a good start. https://fio.readthedocs.io/en/latest/fio_doc.html https://github.com/aerospike/act

P99 latency at a constant read/write rate is exactly the test that Aerospike ACT benchmark performs. https://github.com/aerospike/act Aerospike has been engineered to perform well in this exact space. P99 <8ms over multiple TB of durable storage under a constant read/write rate.

Not directly related to TRIM, but AeroSpike has a nice test suite for SSDs, probing for IOPS and latency: https://github.com/aerospike/act They share their test results for both physical and cloud-based storage, I figured this would be of interest: http://www.aerospike.com/docs/operations/plan/ssd/ssd_certif...