Sorry couldn’t find this number in the blogs, what’s the latency of distributed (cross-tablet) transactions, 99%, min, mix, avg, within a medium size cluster under moderate load?
hi @bro
This is a complex scenario that depends on multiple factors: concurrency on single rows, % of data in ram, how many tablets and leader servers the query interacts, cpu performance, wal, inter-region/zone,network congestion/latency etc.
As a general point, we can explain how the read/write/transaction path works:
- Single key read path Read I/O path | YugabyteDB Docs
- Single key write path Write I/O path | YugabyteDB Docs
- How isolations levels work/conflict Transaction isolation levels | YugabyteDB Docs
- Single row transaction Single-row transactions | YugabyteDB Docs
- Distributed transaction overview Distributed transactions | YugabyteDB Docs
- Distributed transaction read/write path Transactional I/O path | YugabyteDB Docs
The best way to go about it, is to:
- look how your app works in a high level
- know the internals so you have an idea to group data better and lower as much the number of network hops
- test & repeat depending on the numbers
We can help on all these steps so you can go faster and don’t have to learn all of it.