This message was deleted.

Hi Aviad, I think this is standard behavior. Time spent waiting for segments to be scanned contributes to query response time. The ways I know to improve this are: • reduce the number of segments needing to be scanned (e.g. range partitioning for better segment pruning, compaction to reduce fragmentation) • increase the number of processes that are available to scan segments. • configure (via secondary partitioning) your segments so that they scan faster I would suggest check for excess fragmentation, appropriate segment granularity, and appropriate secondary partitioning strategy.

Hello, Thanks for the insightful response. If I understood correctly, you're suggesting the following ways to improve the situation: 1. Add More Resources: Increase the number of processes that can scan segments, which in essence means increasing the capacity of our system to handle more queries. 2. Database Optimization: Work on database maintenance tasks such as indexing, defragmentation and partitioning. This includes actions like range partitioning for better segment pruning, compaction to reduce fragmentation, and configuring segments for faster scanning through secondary partitioning. So, the key takeaway is that improving system resources and maintaining the health of the database could alleviate the problem. Have I understood this correctly?

yes, correct; in general you're describing a "too much work to do" problem, so we can address it by adding more resources (more ability to do work), or by optimizing things (less work to do)