Versions Compared

Old Version 35

changes.mady.by.user Vladimir Ozerov Ozerov

Saved on

compared with

New Version Current

changes.mady.by.user Denis Magda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Improved query latency, as we will be able to skip much more partitions than now (only backup partitions are skipped for now)
  2. Improved thin client latency - it will be possible to send requests to target node, thus saving one network hop.
  3. Decreased page cache pressure - less data to read, less data to evict, less number of page locks
  4. Improved system throughput, as less total CPU and IO operations will be required to execute optimized query
  5. 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

...