Reads canceled before filesystem I/O; excluded from the hit-rate denominator.
OptionalmaxSize?: numberConfigured byte budget (fixed OPFS/disk cap).
OptionaloversizedWriteSkipped?: numberOptionalquotaWriteSkipped?: numberOptionalevictions?: numberOptionalwriteFailures?: numberOptionalcorruptedEntries?: numberOptionalmetadataParseFailures?: numberOptionalorphanedFilesRemoved?: numberBackground L2 write-queue backpressure snapshot. L2 (OPFS) writes are deferred off the fetch critical path and drained at a bounded concurrency; this exposes the queue's live depth / retained bytes / in-flight count and the cumulative count of writes dropped by either overflow policy.
Bytes fetched over the network (L3) — excludes cache-served bytes.
Count of actual network fetches (L3).
Current network bandwidth (bytes/sec, ~10s sliding window).
Cumulative bytes delivered to demand callers across ALL tiers
(L1 + L2 + network). Unlike bytesTransferred, this stays
non-zero on a warm/cache-served reload, so the monitor's
"data loaded" figure reflects real I/O even with zero network.
Count of demand reads served across all tiers.
Per-tier demand-hit counters (user demand only — prefetch traffic
is excluded). Each user-demand getResult call increments exactly
one of l1Hits, l2Hits, or networkRequests. Combined with the
L0 provider's stats, this lets the monitor surface an effective
demand hit-rate rather than the L1-only ratio.
Cache health snapshot. Surfaced by the data monitor status badges and debug diagnostics.
Validation mode the dataset is using (or 'none' if external + no TTL).
Wall-clock millis at last successful validation, or null.
true when the dataset has no content_hash AND no TTL is
configured — surfaced as a UI warning since the cache may be
stale indefinitely.
S2: true when OPFS is available and L2 is operational, or
when caching is disabled (no L2 expected). false only when
caching is enabled but OPFS could not be acquired — drives the
opfs-unavailable status badge.
S4: number of times ?clearCache triggered a clearAll on init
for this store. Increments at most once per store lifetime today
but typed as a counter so future re-init paths stay observable.
Snapshot returned by
MultiLevelCachingStore.getStats(). Aggregates the L1 segmented-LRU stats, the L2 OPFS stats, network counters, per-tier demand-hit counters, cache health (validation mode + OPFS availability), and the?clearCacheinvocation counter.Consumed by the data-loading monitor, the debug overlay, and the cache E2E suite.