Home → Users Manual → Filters → Filter Caching and Performance
6.16. Filter Caching and Performance
Updated: 3 Sep 2026, 10:06 PM EDT
The count beside a filter name in the left navigation is cached. How long depends on how heavily the filter is used:
| Filter usage | Cache duration |
|---|---|
| Top 5% most viewed | 5 minutes |
| 75th–95th percentile | 10 minutes |
| 50th–75th percentile | 30 minutes |
| Below 50th percentile | 60 minutes |
Two things worth knowing about how those tiers are set. They are recalculated once a day by a scheduled maintenance job, so a filter's tier reflects yesterday's usage. And only filters with Display count in Workspace switched on are ranked at all — if fewer than ten filters have usage data, every filter simply gets 5 minutes.
Never cache the workspace display count in Edit Filter > Options tab does not quite mean never. It takes the filter out of the tier schedule above and caps its count at a one-minute cache instead — so the number can still be up to a minute old, rather than up to an hour. Use it only where a nearly live count matters; it costs database work on almost every workspace load.
Caching only ever affects the count. Opening a filter always runs it fresh against the database — the rows you see are never served from a cache — and running it replaces the cached count. So a stale number in the left navigation corrects itself the moment you click it.