[CASSANDRA-8931] IndexSummary (and Index) should store the token, and the minimal key to unambiguously direct a query

• Type: Improvement
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Legacy/Local Write-Read Paths
• Labels: performance
• Assignee: Unassigned
• Reporter: Benedict Elliott Smith
• Created: 07/Mar/15 12:21
• Updated: 07/Mar/23 10:53

Description

Since these files are likely sticking around a little longer, it is probably worth optimising them. A relatively simple change to Index and IndexSummary could reduce the amount of space required significantly, reduce the CPU burden of lookup, and hopefully bound the amount of space needed as key size grows. On writing first we always store the token before the key (if it is different to the key); then we simply truncate the whole record to the minimum length necessary to answer an inequality search. Since the data file contains the key also, we can corroborate we have the right key once we've looked up. Since BFs are used to reduce unnecessary lookups, we don't save much by ruling the false positives out one step earlier.

An improved follow up version would be to use a trie of shortest length to answer inequality lookups, as this would also ensure very long keys with common prefixes would not significantly increase the size of the index or summary. This would translate to a trie index for the summary keying into a static trie page for the index.

Issue Links

• relates to: CASSANDRA-9786 Our index file seeks can be directed to the page most likely to contain the record, and read exactly one page
• relates to: CASSANDRA-9754 Make index info heap friendly for large CQL partitions