Larger memtable means mor time during flushes and larger heap means longer GC pauses. You can see these in system log
Sent from my iPhone > On May 24, 2017, at 11:31 AM, preetika tyagi <preetikaty...@gmail.com> wrote: > > Hi, > > I'm experimenting with memtable/heap size on my Cassandra server to > understand how it impacts the latency/throughput for read requests. > > I vary heap size (Xms and -Xmx) in jvm.options so memtable will be 1/4 of > this. When I increase the heap size and hence memtable, I notice the drop in > throughput and increase in latency. I'm also creating the database such that > its size doesn't exceed the size of memtable. Therefore, all data exist in > memtable and I'm not able to reason why bigger size of memtable is resulting > into higher latency/low throughput. > > Since everything is DRAM, shouldn't the throughput/latency remain same in all > the cases? > > Thanks, > Preetika --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
