I'd be really interested to know what sort of performance or load improvements you see by doing client side partitioning. Please post back some results if you've tried that strategy.
On Thu, Dec 4, 2014 at 11:46 AM, Tyler Hobbs <ty...@datastax.com> wrote: > > On Thu, Dec 4, 2014 at 11:50 AM, Dong Dai <daidon...@gmail.com> wrote: > >> As we already did what coordinators do in client side, why don’t we do >> one step more: >> break the UNLOGGED batch statements into several small batch statements, >> each of which contains >> the statements with the same partition key. And send them to different >> coordinators based >> on TokenAwarePolicy? This will save lots of RPC times, right? >> >> The reason I asked is I have a use case where importing huge data into >> Cassandra is a very common case, and all these importing do not need to >> be atomic. >> > > Yes, what you suggest is basically ideal. I would do exactly that. > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> >
