0.35.4

docs/DASHBOARD.md

@@ -25,10 +25,20 @@ Optional quick-health tiles (since 0.35.2, hidden by default; enable them in the
 
 Enabled tiles are added at the end of the Overview, so the standard block layout does not change.
 
-The **Remember choice** control next to the history sample count shows a status only when the current choice is temporary (not saved) or briefly after saving.
+The Overview history sample count is saved in the browser immediately when the selection changes; no separate confirmation button is required.
+
+The sidebar application-status indicator runs a lightweight self-check from the live status already used by the dashboard. Green means healthy, amber means attention is needed, and red means a problem was detected; click it to see API, listener, backend and logging details.
 
 The unlocked Overview layout exposes a single **Save and lock** action (plus Cancel), removing the redundant lock-and-save button.
 
+### Arranging blocks
+
+After **Unlock layout**, every block shows a compact toolbar: the **⠿** handle, width **− / +**, and **×** to hide it (wider blocks also show **← / →**).
+
+- **Drag:** grab the ⠿ handle (mouse, pen or touch). The block lifts and follows the pointer, and a dashed frame of the same width shows exactly where it will land; neighbouring blocks glide aside instead of jumping. Release to drop, or press **Esc** to return the block to its previous place. Dragging near the top or bottom edge of the window scrolls the page.
+- **Keyboard:** focus the ⠿ handle and use the arrow keys to move the block one position.
+- **Fill gaps:** a saved custom layout keeps blocks in exactly the order you arranged them, so a wide block that does not fit at the end of a row leaves a visible gap instead of other blocks silently moving into it. Use **Fill gaps** to pack blocks into empty space once; nothing is stored until **Save and lock**.
+
 **Dashboard Presets** supports up to **16 named layouts per administrator**. Save, load, rename, overwrite and delete presets; a factory layout can be restored. Presets preserve the dashboard arrangement, not the live traffic values. Interface theme, scale and other display settings are also account-scoped and do not alter proxy routing or rewrite shared configuration.
 
 ## Editing configuration safely

docs/FEATURES.md

@@ -76,7 +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.
-- Customizable dashboard layouts and saved presets.
+- 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`).
 - Stored JSON access logs with search syntax, per-Vhost log files and an error log.

docs/PERFORMANCE.md

@@ -70,7 +70,16 @@ Choose mimalloc only when all of these apply:
 - throughput under that turnover matters more than memory;
 - the server has at least 30% RAM headroom above the configured HOT cache size.
 
-Otherwise keep the default. The system allocator returns memory from evicted cache entries to the operating system right away, so process memory stays close to the configured cache size.
+Otherwise keep the default. The system allocator returns memory from evicted cache entries to the operating system shortly after eviction, so process memory stays close to the configured cache size.
+
+**Since 0.35.4** the default build returns freed memory to the operating system at most four times per second (plus the regular cache maintenance pass) instead of after every eviction. Most of the system allocator's slowdown under turnover came from these repeated trims, so the gap to mimalloc is now much smaller. Measured on the same 2 vCPU machine, one core, 256 MiB HOT cache filled with 100 KiB objects and every request a new URL:
+
+| Build | RSS after load | Throughput under cache turnover |
+|---|---:|---:|
+| 0.35.3, system allocator | 595 MiB | 2,900 req/s |
+| 0.35.4, system allocator | 639 MiB (+7%) | 7,000 req/s (2.4×) |
+
+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.
 
 ## Production tuning