Repository navigation
Backend: bounded application cache with expiry and metrics - #6107
Conversation
Typed Cache with size/weight bounds, write/access/per-entry expiry, deduplicated concurrent loads, invalidation, removal listeners and metrics in the backend metrics API. JVM tests use a controllable clock; the ParparVM self-test covers the same API natively. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Developer Guide build artifacts are available for download from this workflow run:
Developer Guide quality checks: |
Cloudflare Preview
|
|
Compared 191 screenshots: 191 matched. Native Android coverage
✅ Native Android screenshot tests passed. Native Android coverage
Benchmark ResultsDetailed Performance Metrics
|
|
Compared 227 screenshots: 227 matched. |
✅ Continuous Quality ReportTest & Coverage
Static Analysis
Generated automatically by the PR CI workflow. |
|
Compared 206 screenshots: 206 matched. Benchmark ResultsDetailed Performance Metrics
|
|
Compared 206 screenshots: 206 matched. Benchmark ResultsDetailed Performance Metrics
ParparVM vs HotSpot (JDK 25): Windows x64Runner CPU: Intel64 Family 6 Model 207 Stepping 2, GenuineIntel (baseline 2 improvements past the baseline (not a failure; rebaseline to lock them in):
Ratios are ParparVM / JDK 25: below 1.00x ParparVM is faster (time) or smaller (RAM). Median of 5 interleaved, paired rounds; every run's output was verified. A ratio more than 20% (time) / 25% (RAM) above its baseline in
A change that moves performance ON PURPOSE records the new baseline in Result: no regression (improved past the baseline: consider rebaselining) |
Implements #5996.
com.codename1.backend.Cache: size/weight bounds, expire after write/access, per-entry expiry, atomic deduplicated loads (VT-safe waiting), invalidation, removal listeners run outside the lock, metrics undercache.<name>.*.CacheTest, controllable clock) and ParparVM self-test checks.🤖 Generated with Claude Code