Documentation

Caching & performance

Every chart result flows through a stale-while-revalidate cache, and a regeneration lock prevents stampedes — so dashboards stay fast and your database stays calm.

Step by step

1Open Glimpse BI → Settings → Performance.
2Set Cache TTL (default 15 minutes) — how long a chart result is served before it’s refreshed.
3Set the stale window multiplier — how long stale data may be served past TTL while a refresh runs.
4Tune Query timeout and Max rows to bound expensive queries.
5For very heavy charts, enable Materialization (Pro) to pre-compute on a schedule.

yoursite.com/wp-admin/admin.php?page=glimpsebi-settings

Glimpse BI Settings — cache TTL, query limits, and schema discovery controls.

Stale-while-revalidate

A chart result is wrapped in an envelope keyed by the chart, its definition, and its runtime parameters. Within the TTL it’s served instantly; once stale, the first viewer triggers a background refresh while others keep getting the cached value — so a slow query never blocks the page.

Stampede protection

A regeneration lock ensures only one process recomputes a given chart at a time; everyone else serves stale within the stale window or briefly waits on a cold miss. Where a persistent object cache is available the plugin uses it automatically, falling back to transients otherwise.

Reference

Default TTL900s (15 min)

Stale windowTTL × multiplier (default ×2)

Schema cache1 hour

BackendObject cache if present, else transients

StampedeAtomic regeneration lock

NextAsk (AI)

Install free in a minute. Ask when you’re ready.

Start with the free plugin from WordPress.org. Upgrade to Pro to unlock Ask, pre-computed charts and Editor roles.

Get the free plugin See Pro plans