News for hackers. Stuff that matters.
Re:YCSB Benchmark Results for YugaByte and Apache Cassandra by rkarthik007 on Monday November 13, 2017 @10:51AM (#15687298)
Great points, thanks @doikor! Will try these.

It would be nice if some of these were the defaults as opposed to some settings folks have to change - say by running a "./configure" or some such.

In this case, for example, it felt a little weird that the machine type which had enough cores had 60GB RAM, and giving only around 10-20GB to Cassandra "felt" wrong, but turns out the exact opposite is true! YugaByte is in C++ and can handle much larger heaps.

Re:YCSB Benchmark Results for YugaByte and Apache Cassandra by arielweisberg on Monday November 13, 2017 @03:21PM (#15689853)
Java's garbage collected heap is not the full extent of memory used by Cassandra. Cassandra can use as much memory as you can throw at it.

File system cache, in process decompressed page cache, key and row cache, off heap memtables etc. There are several different mechanisms for using memory that isn't on the garbage collected heap.

^ This is not a qualitative assessment of how Cassandra uses memory.