Skip to main content

 –

Increasingly slower read operations

Suggest edit Updated on March 11, 2021

Read operations take a prolonged time, which impacts system performance.

SSTables reduce read capacity because records might be spread across several SSTables, as a result of frequent write operations, modifications, and deletions.

  1. Check the number of SSTables per column family (table) by using the nodetool tablestats command.
  2. Analyze the outcome to determine the root cause of the issue.
    Depending on the nodetool tablestats outcome, you might want to perform such actions as adjusting your compaction throughput, expanding the memory size for file caching, and so on. For more information, see the Apache Cassandra documentation.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us