Store serialized core in runtime cache

2026-07-16 21:10:09 +00:00
parent ee2177f4b4
commit 93c701c6c7
2 changed files with 7 additions and 2 deletions
@@ -140,7 +140,10 @@ changing core-first, unit-load-order symbol resolution.
 Each FastCGI child initializes its process-local Wasmtime engine after fork and
 before entering the accept loop. This preserves Wasmtime's fork boundary while
 preventing the first request assigned to each worker from paying engine startup.
-Startup duration or failure is written to the service log.
+Startup duration or failure is written to the service log. The serialized core
+module lives in the configured writable cache root rather than beside the
+possibly root-owned deployed `core.wasm`; freshness still uses the deployed
+artifact's metadata.

 `request_perf()` reports worker module-cache hits and misses and divides a miss
 into artifact lookup, wasm read, custom-section parse, serialized-module