v0.36.8

docs/FEATURES.md

@@ -76,6 +76,7 @@ RustProxy is a single service that combines a reverse proxy, a static/PHP web se
 ## Monitoring and logs
 
 - Overview dashboard with requests per second, bandwidth, status codes, error share, cache hit ratio, protocol mix, system load, backend health, requests rejected by limits and nearest certificate expiry.
+- Optional **Memory breakdown** card: process RSS split into cache data, cache bookkeeping, cache buffers, allocator-held free memory, mapped files and the rest of the process, with glibc heap statistics and an "outside cache" trend for spotting leaks.
 - Customizable dashboard layouts (drag-and-drop with a live drop placeholder, keyboard moves, per-block width, explicit gap filling) and saved presets.
 - Per-Vhost, per-backend, per-Web-Service and per-Stream statistics.
 - Live request log in the browser and in the terminal (`--livelogs`).

docs/PERFORMANCE.md

@@ -81,6 +81,10 @@ Otherwise keep the default. The system allocator returns memory from evicted cac
 
 The mimalloc rows above were measured with 0.35.2 and a different object mix; re-measure on your own workload before choosing the optional build.
 
+### Where the memory goes
+
+Process memory is always larger than the configured HOT cache. The HOT size already includes RustProxy's estimate of per-object bookkeeping (index, keys, headers), but not allocator rounding and fragmentation, connection and TLS buffers, the runtime, logs or GeoIP data. Enable the optional **Memory breakdown** Overview card to see the split for your workload: if the "Outside cache" trend stays flat while the cache is full, the difference is overhead or fragmentation; a steady rise points to memory that is not released. For reference, Varnish documents about 1 KiB of per-object overhead outside its storage size and notes that total use can reach about twice the configured storage.
+
 ## Production tuning
 
 | Setting | Recommendation |