Thanks for the information, Yuki,
OK, I understood that the write latency is basically a table metric, not a
keyspace metric. Looks like the query tracing is for analyzing each
individual request, but it provides exactly the breakdown I want.
Thanks for your help! Let me also think about
Hi Rei,
As you pointed out, table (column family) metric only tracks memtable
and row cache update.
Update is done through Mutation object that can have several column
families at once.
And the unit of commit log is Mutation, so we may first write commit
log of several tables and then we update
