[ https://issues.apache.org/jira/browse/IGNITE-21906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandr Polovtcev resolved IGNITE-21906. ------------------------------------------ Resolution: Won't Fix > Consider disabling inline in PK index by default > ------------------------------------------------ > > Key: IGNITE-21906 > URL: https://issues.apache.org/jira/browse/IGNITE-21906 > Project: Ignite > Issue Type: Improvement > Reporter: Ivan Bessonov > Assignee: Aleksandr Polovtcev > Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > In aipersist/aimem we attempt to inline binary tuples into pages for hash > indexes by default. This, in theory, saves us from the necessity of accessing > binary tuples from data pages for comparison, which is slower than comparing > inlined data. > But, assuming the good hash distribution, we would only have to do the real > comparison for the matched tuple. At the same time, inlined data might be > substantially larger than hash+link, meaning that B+Tree with inlined data > has bigger height, which correlates with slower search speed. > So, we have both pros and cons for inlining, and the only real way to > reconcile them is to compare them with some benchmarks. This is exactly what > I propose. > TL;DR: force inline size to be 0 for hash indices and benchmark for put/get > operations, with large enough amount of data. -- This message was sent by Atlassian Jira (v8.20.10#820010)