...
- Improved query latency, as we will be able to skip much more partitions than now (only backup partitions are skipped for now)
- Improved thin client latency - it will be possible to send requests to target node, thus saving one network hop.
- Decreased page cache pressure - less data to read, less data to evict, less number of page locks
- Improved system throughput, as less total CPU and IO operations will be required to execute optimized query
- Improved thin client latency - it will be possible to send requests to target node, thus saving one network hop.
Partition pruning is already implemented in Apache Ignite in very simplified form [1]. Only WHERE condition with equality is considered and only for SQL queries without joins. We should expand it further.
[1] https://issues.apache.org/jira/browse/IGNITE-4509
...