[IGNITE-14936] Benchmark sorted index scan vs table's partitions scan

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: sql
• Labels: ignite-3
• Epic Link: SQL indexes 3.0
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Taras Ledkov
• Created: 18/Jun/21 09:21
• Updated: 26/Jul/22 11:34
• Resolved: 26/Jul/22 11:34

Description

We have to decide what are data structures is used for PK and table scan.
Possible cases:

• table partitions sorted by plain bytes/hash (in fact: unsorted);
• table partitions sorted by PK columns;
• PK sorted index (one store for all partitions on the node).

All cases have pros and cons. The choice should be based on benchmarks.

Issue Links

• is blocked by: IGNITE-14935 Introduce Index Manager
• is part of: IGNITE-14925 Sorted indexes engine