How the index stays fresh

The site reports changes to BitFacet itself (the bitfacet.update plugin), and the filter sees them from the next request:

Visitors never see a half-built index: a new build is written next to the old one and swapped by renaming one file.

Rebuilding

Build history (who, when, why, products, time, memory, error) and the error log are on the Index tab.

Where the index lives

In the bitfacet.index_path folder (default core/components/bitfacet/data/index/), one folder per set. The index can be deleted — it will be rebuilt. Read modes (bitfacet.storage):

Large catalogs

Measured on 369k products (15 filters): rebuild 8–12 s and about 410 MB of memory, index 52 MB, filter query 2–11 ms, page 21–34 ms. Raise the limits for large catalogs:

Products in the setmemory_limitopcache.memory_consumption
up to 50,000256M128M
up to 150,000256M256M
up to 400,000512M512M

Index settings

SettingDefaultWhat it does
bitfacet.storageautoIndex read mode: auto, opcache, file.
bitfacet.journal_max100Changes kept in the journal before a full rebuild.
bitfacet.rebuild_delay300Seconds after the first change before the index is rebuilt.
bitfacet.rebuild_max_age24Every this many hours cron rebuilds the index completely (0 — not by age).
bitfacet.build_keep_days30Days to keep build history (0 — forever).
bitfacet.cron_enabled, bitfacet.cron_intervalyes, 5Cron is on; interval in minutes for the crontab line and the "not run for long" check.
bitfacet.index_path, bitfacet.sets_pathin core/components/bitfacet/data/Index and set folders. Changed on the Settings tab; site folders (root, core, assets) cannot be chosen.