Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Increasingly slower read operations

Updated on April 5, 2022

This content applies only to On-premises and Client-managed cloud environments

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.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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