cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Petrus Gomes <petru...@gmail.com>
Subject Re: Cassandra seems slow when having many read operations
Date Thu, 13 Jul 2017 18:02:41 GMT
How is your Percent Repaired  when you run " nodetool info" ?

Search for :
"reduced num_token = improved performance ??" topic.
The people were discussing that.

How is your compaction is configured?

Could you run the same process in command line to have a measurement?

Thanks,
Petrus Silva



On Thu, Jul 13, 2017 at 7:49 AM, Felipe Esteves <
felipe.esteves@b2wdigital.com> wrote:

> Hi,
>
> I have a Cassandra 2.1 cluster running on AWS that receives high read
> loads, jumping from 100k requests to 400k requests, for example. Then it
> normalizes and later cames another high throughput.
>
> To the application, it appears that Cassandra is slow. However, cpu and
> disk use is ok in every instance, row cache is enabled and with almost 100%
> hit rate.
>
> The logs from Cassandra instances doesn't have any errors, nor tombstone
> messages or something liked that. It's mostly compactions and G1GC
> operations.
>
> Any hints on where to investigate more?
>
>
> Felipe Esteves
>
>
>
>
>

Mime
View raw message