Hi, Ben
Thank you for your reply.
> The AWS instance type you are using is not appropriate for a production
workload
I agree with you. I use it for a just verification of the C* behavior.
So I really want to understand the actual mechanism of the write request
blocking. I would appreciate if
A few thoughts on the larger problem at hand.
The AWS instance type you are using is not appropriate for a production
workload. Also with memtable flushes that cause spiky write throughput it
sounds like your commitlog is on the same disk as your data directory,
combined with the use of non-SSD
Hi,
I'm investigating the read/write performance of the C* (Ver. 2.2.8).
However, I have an issue about memtable flushing which forces the spiky
write throughput. And then it affects the latency of the client's requests.
So I want to know the answers for the following questions.
1. Is there any
