[planckscnst]

I wonder if they will consider expanding the cloud report to things that are not necessarily relevant to Cockroach labs use-case. In my work, latency to the block store (especially outliers) is very relevant. It would be great to see latency distributions of various workloads (sequential/random and read/write/mixed) to the patform's distributed block store.

edit: I missed that 95th percentile latency for read and write was included. That is helpful; I also typically look at p99.99 and p100.

[londons_explore]

You can tradeoff talk latency vs cost yourself easily.

For example, you could have two copies of your data in the block store, and issue reads to both simultaneously, and use whichever returns first. Suddenly, your 99% latency becomes your 99.99% latency...

You can do the same for writes (albeit a bit more complex).

[planckscnst]

Yes, the cost/latency trade-off is exactly why this can be interesting. Significantly fewer or less-impactful outliers can save a lot of money (or allow a better SLA with the same cost).

[awoods187]

We can consider expanding this in our testing next year! Glad you found it helpful