On 2019-09-06 11:02, Oleksandr Shulgin wrote:
On Fri, Sep 6, 2019 at 11:00 AM wrote:
- reads => as much as possible - huge stream of requests
- data => 186GB on each node
- the reads are unpredictable
- there's (in the cluster) about 6 billions of records
I wonder though, if it makes sense
...@xvalheru.org
Sent: Friday, September 6, 2019 3:00 AM
To: user@cassandra.apache.org
Cc: Jeff Jirsa
Subject: Re: Cassandra JVM configuration
- reads => as much as possible - huge stream of requests
- data => 186GB on each node
- the reads are unpredictable
- there's (in the cluster) about 6 bi
On Fri, Sep 6, 2019 at 11:00 AM wrote:
> - reads => as much as possible - huge stream of requests
> - data => 186GB on each node
> - the reads are unpredictable
> - there's (in the cluster) about 6 billions of records
>
I wonder though, if it makes sense to use Cassandra for a read-only
- reads => as much as possible - huge stream of requests
- data => 186GB on each node
- the reads are unpredictable
- there's (in the cluster) about 6 billions of records
I'll try change the garbage collector.
Thanks
Pat
On 2019-09-05 16:38, Jeff Jirsa wrote:
Lot of variables
- how many
Thanks for suggestion.
Pat
On 2019-09-05 16:19, ZAIDI, ASAD wrote:
Every use case is unique so as such jvm configs go with it. 8G may or
may not be sufficient depending on live data you keep in, or fetch to
memory. You can opt using G1GC, that is easy to start with.
Some good suggestions
Lot of variables
- how many reads per second per machine?
- how much data per machine?
- are the reads random or is there a hot working set?
Some of the suggestions online are old.
CASSANDRA-8150 has some old’ish suggestions if you’re running CMS collector.
Running > 16G heap should consider
Every use case is unique so as such jvm configs go with it. 8G may or may not
be sufficient depending on live data you keep in, or fetch to memory. You can
opt using G1GC, that is easy to start with.
Some good suggestions are made if you want to try G1GC or stick with CMS. Take
a look at [
