Do you mean on writes? Yes, your timeouts must be so that your write
batch could complete until timeout elapsed. But this will lower write
load, so reads should not timeout.
Best regards, Vitalii Tymchyshym
06.01.12 17:37, Philippe написав(ла):
But you will then get timeouts.
Le 6 janv. 2012 15:17, "Vitalii Tymchyshyn" <tiv...@gmail.com
<mailto:tiv...@gmail.com>> a écrit :
05.01.12 22:29, Philippe написав(ла):
Then I do have a question, what do people generally use as
the batch size?
I used to do batches from 500 to 2000 like you do.
After investigating issues such as the one you've encountered
I've moved to batches of 20 for writes and 256 for reads.
Everything is a lot smoother : no more timeouts.
I'd better reduce mutation thread pool with concurrent_writes
setting. This will lower server load no matter, how many clients
are sending batches, at the same time you still have good batching.
Best regards, Vitalii Tymchyshyn
