telexed ~ c / 35605736-16fradar:50 · otherLIVE
← back
NO.
#35605736
Topic
OTHER
Source
GeekNews
Published
2026-05-11 06:02:24
Importance
★ 5/10 — radar 50
Replacing a `3GB` `SQLite` dictionary with a `10MB` `FST` binary
FIG-3561:1

Replacing a `3GB` `SQLite` dictionary with a `10MB` `FST` binary

When autocomplete data explodes into tens of millions of forms, static FST indexing beats SQLite FTS on distribution cost. For read-heavy search, this is a strong pattern for mobile and edge delivery.

[ KEY POINTS ]
  1. A Finnish-English dictionary grew to 40M-60M entries after inflection expansion, pushing trie-based search past practical limits.
  2. A temporary SQLite FTS approach was fast enough at query time, but shipping an initial 3GB download broke usability.
  3. A compiled FST binary cut the payload to about 10MB, turning a search structure into something app-bundle-sized.
  4. This pattern fits datasets that are mostly static and prefix-search-heavy, where update flexibility matters less than footprint.
Originalnews.hada.io/topic?id=29379Read original →

// related