What sort of slicing are you doing? This will impact CPU usage. Michael
Huming Wu<[email protected]> wrote: > I did some performance test and I am not impressed :). The data set is > 880K unique keys and there are 4 columns with 2 columns being string > and the other 2 are integers (from client side, to the backend it is > all byte[]). After high throughput set (very fast), 220MB are injected > via batch_insert. I restarted the cassandra and started a client > calling get_slice at 5000rps with 100 connections. [...] > a) Read is too CPU intensive. With the actual peak rps around 3000, > the CPU usage is 70% already. I doubt it I can double the rps and have > the same read latency. [...] > Any comments on those numbers?
