Type: New Feature
Fix Version/s: 0.7 beta 1
For small heaps (including our out-of-the-box 1G) we want to allow reducing this from the automatic (1 + 2 * DatabaseDescriptor.getAllDataFileLocations().length); having 3 memtables in the queue, plus another being written, is over 200MB which is a significant amount of data for the GC to chew through (see
For large heaps, we might also want to allow increasing this value, to accommodate load spikes better.
Unfortunately making this configurable at runtime does not appear to be an option due to the lack of a setCapacity method on any of the BlockingQueue classes.