CompactGUI VS tantivy

CompactGUI

Also, check out CompactGUI. It's a more user-friendly and efficient way of using Windows' built-in compression to cut the game's file size almost in half. It makes load times marginally longer (like 5-10%) and needs to be redone every few updates to keep the size down, but it works.

You can chuck compact.exe at it by hand (use the /exe option), or if you'd prefer to avoid the command line there's my Compactor tool, or the venerable CompactGUI.

You can also just use compactGui smaller filesizes without having to remove dialogs or cutscenes or anything. Obviously how much space is regained depends on how well it was compressed originally. With triple A titles perhaps getting 10% back, while things like ark can literally be shrunk by hundreds of gigs.

Not really related to your question but if you want to try and save some space you can give this a go, I've used it before and never had any issues. https://github.com/IridiumIO/CompactGUI

Meet you new best friend. https://github.com/IridiumIO/CompactGUI

Tantivy - a full-text indexing library written in Rust. Has a great performance and featureset.

By this I presume you mean build a search index that can retrieve results based on keywords? I know certain databases use Lucene to build a keyword-based index on top of unstructured blobs of data. Another alternative is to use Tantivy (https://github.com/quickwit-oss/tantivy), a Rust version of Lucene, if building search indices via Java isn't your cup of tea :)

Both libraries offer multilingual support for keywords, I believe, so that's a benefit to vector search where multilingual embedding models are rather expensive.

We also implemented our schemaless columnar storage optimized for object storage.

The inverted index and columnar storage are part of tantivy [0], which is the fastest search library out there. We maintain it and we decided to build the distributed engine on top of it.

[0] tantivy github repo: https://github.com/quickwit-oss/tantivy

The issue for geo search is here: https://github.com/quickwit-oss/tantivy/issues/44

Search index : Custom-built using tantivy.

The roaring bitmap variant is used only for the optional index (1 docid => 0 or 1 value) in the columnar storage (DocValues), not for the inverted index. Since this is used for aggregation, some queries may be a full scan.

The inverted index in tantivy uses bitpacked values of 128 elements with a skip index on top.

> I didn't follow the rest of your comment, select is what EF is good at, every other data structure needs a lot more scanning once you land on the right chunk. With BMI2 you can also use the PDEP instruction to accelerate the final select on a 64-bit block

The select for the sparse codec is a [simple array index access](https://github.com/quickwit-oss/tantivy/blob/main/columnar/s...), that is hard to beat. Compression is not good near the 5k threshold though.

Hi /r/rust, I’m a SWE on Etsy’s Retrieval Systems team where we’re building a platform based on rust and tantivy (https://github.com/quickwit-oss/tantivy). We’re looking to bring two new engineers onto the team.

Quick Search: Easily find specific notes with Velo's fuzzy-search feature, powered by tantivy. tantivy might have been a little overkill, but it was really easy to integrate.