| ... | ... | @@ -65,3 +65,18 @@ benefit requires cache hits beyond those already served by RAM; a virtualized |
| 65 | 65 | correctness test is not a physical SSD/HDD performance benchmark. |
| 66 | 66 | |
| 67 | 67 | See [OpenZFS caching documentation](https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Pool%20Structure/Caching.html). |
| 68 | |
| 69 | ## Production rollout |
| 70 | |
| 71 | Release `40a5a3b0e724162a` activated the cache on 2026-10-20 from commit |
| 72 | `d7a27fd3`, after backup `20261020T195536Z-88c9a1`. The cache was online at its |
| 73 | configured capacity, and restarting its setup service preserved its device |
| 74 | GUID and contents. The pool stayed healthy with no cache I/O or checksum errors. |
| 75 | Approximately 50 GiB remained free on the OS SSD. |
| 76 | |
| 77 | All six previously running guests retained their VM IDs. A new disposable |
| 78 | guest placed its disk under `/srv/vm`, displayed its firmware shell through |
| 79 | the production browser console, accepted a keyboard command, and shut down |
| 80 | normally. Its definition and disk were removed afterward. The release's |
| 81 | service health checks passed. Cache warming was observed; these checks do not |
| 82 | establish a Windows startup speedup. |