3 ms·

Cassandra's out. It's whole design is for work loads with lots of writes mixed in.

• riffraff 16y ago
  being really good at writes does not mean it's really bad at reads, it is actually pretty good (in our cassandra cluster we have ~1ms latency which may be tolerable or not but it's not a lot) EDIT: and we don't have row caching enabled
• strlen 16y ago
  Not really the case. There all sorts of optimizations in place (row caching, Bloom filters) that give adequate read performance. Is the read performance suitable for the OP, given his workload, his hardware (i.e., the amount of RAM he can give to Cassandra, the speed of his disks)? I don't know, but the only way to find out is experimentally.