Repository navigation
1.8.2 (2026-09-11)
This release keeps your dashboard history intact across storage server restarts and fixes a bug that slowly shrank daily totals.
The nightly rollup now mirrors each site's daily counters into the WordPress database. When the storage server restarts or evicts cold keys, which is common in the recommended setup without persistence, the history is automatically restored, so the long-range views on the Status dashboard no longer go blank while the cache regenerates. Clearing metrics still clears the mirror, so a deliberate wipe stays wiped. Only the per-hour detail recorded since the last nightly run is lost on a restart; the documentation covers this trade-off and how to retain that too.
A separate bug in the same rollup caused daily totals to shrink over time: the nightly job was rewriting every past day's total from its hourly buckets, including the day at the retention edge whose earliest hours the previous prune had already removed. Days fully covered by hourly data are still rewritten as before; the day at the edge and any older days now keep their existing total instead.
Features
- metrics: keep the daily history when the storage server restarts (a56173e)
- storage: expose the shared body hash and meta size per cache entry (d3731fb)
Bug Fixes
- cache: keep pages cacheable at the edge for the whole local cache lifetime (b938b92)
- metrics: keep daily totals intact at the hourly retention edge (d166ae3)
- storage: expire cache entries by their own custom TTL (58f2951)
Dependencies
- millibase: update MilliBase to 2.11.0 (c35f7af)
Performance Results
Loading 6.2x faster with MilliCache!
| Metric | Without Cache | With MilliCache | Improvement |
|---|---|---|---|
| Server Response (TTFB) | 38ms | 6ms | 84% faster |
| Page Load (LCP) | 80ms | 48ms | 40% faster |
Server Response is the primary metric for page caching. It measures how fast the server delivers the HTML. MilliCache focuses on serving cached pages instantly, eliminating database queries and PHP processing.
Page Load includes frontend rendering time, which depends on themes, scripts, and assets. Content optimization is outside MilliCache's current scope.
Technical Details
Cache Efficiency
- Database queries: 27 → 29
- Response time range: 5ms-47ms (cached) vs 35ms-56ms (uncached)
Cache Generation (First Request)
- Total processing: 35.95ms
- Before template: 18.12ms
- Template rendering: 17.83ms
Test Configuration
- Iterations: 50 (3 warm-up runs discarded)
- Outliers removed: 3
- Timestamp: 2026-09-11T12:01:30.233Z
- Commit: 210bdb4
Regression Analysis
- Status: PASS
- Performance stable: 6.62x -> 6.21x (-6.1%)
- Threshold: 10% slowdown triggers failure