Probably lowest effort is to run the select with tracing enabled - may give
some easy hints
--
Jeff Jirsa
> On Jan 28, 2019, at 7:54 AM, Jonathan Haddad wrote:
>
> Your fastest route might be to run a profiler on Cassandra and get some flame
> graphs. I'm a fan of the async-profiler:
>
>
Your fastest route might be to run a profiler on Cassandra and get some
flame graphs. I'm a fan of the async-profiler:
https://github.com/jvm-profiling-tools/async-profiler
Joey Lynch did a nice write up in the documentation on a different process,
which I haven't used yet:
http://cassandra.apa
Hello,
We have noticed CPU usage spike after several minutes of consistent load
when querying:
- a single column of set type (same partition key)
- relatively frequently (couple hundred times per second, for comparison,
we do an order of magnitude more reads already with much bigger payloads)
- wi
