cangyin
cangyin
Windows x86_64.
@XpecV52 so sorry, I didn't actually fetch it, file in the email has expired.
There is a similar issue #12572
Please check #62706 , if the presented improvement is proper.
Mapping terms to granule IDs will make the inverted index behave like a bloom filter with zero false-positive rate. So I turned to using a 'divisor'.
```sql -- prepare table hackernews with data as per https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/invertedindexes CREATE TABLE hackernews_idx_row_ids AS hackernews ENGINE = MergeTree ORDER BY (type, author); CREATE TABLE hackernews_idx_granule_ids AS hackernews ENGINE = MergeTree...
> would be interesting to see a perf comparison if you have any at hand How to make a perf comparison, is that a `perf diff` ?
I am thinking about throwing current logic away. Because mapping to granule IDs make the inverted index behave like a bloom filter with zero false-positive rate. 1. With bloom filter,...
| Table | Index | Divisor | Size of *.gin_post | Dropped Granules | Index Cold Run | Index Hot Run | Cold Run | Hot Run | | ---...
> what would be the size of posting list if the inverted index type is decclared as inverted(3)? @FrankChen021 Please see updated result above. > would be interesting to see...