udo/uce
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document cached unit import metadata

Browse Source
This commit is contained in:
udo 2026-07-16 19:09:11 +00:00
parent 9b95d00709
commit 8ea1fed38b
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/wasm-runtime-architecture.md
View File

@ -131,6 +131,12 @@ available. If an artifact is cold or stale, dispatch compiles it on demand via
Workers identify cached unit artifacts by nanosecond mtime, ctime, and size. Workers identify cached unit artifacts by nanosecond mtime, ctime, and size.
Whole-second mtime alone is insufficient because a dependency-triggered rebuild Whole-second mtime alone is insufficient because a dependency-triggered rebuild
can replace a wasm artifact within the same second as its prior build. can replace a wasm artifact within the same second as its prior build.
The worker also classifies each compiled module's immutable import descriptors
once when that artifact enters the module cache. Each request still creates its
own import vector, memory/table-base globals, GOT globals and function-table
slots, then runs relocations, constructors, and request-pointer binding. This
removes repeated Wasmtime import-type traversal without sharing request state or
changing core-first, unit-load-order symbol resolution.
Cold module compilation and deserialization are host work, so `load_unit()` Cold module compilation and deserialization are host work, so `load_unit()`
refreshes the epoch deadline before its first guest call. Otherwise a component refreshes the epoch deadline before its first guest call. Otherwise a component
whose compilation outlasted the guest CPU budget would immediately trap in the whose compilation outlasted the guest CPU budget would immediately trap in the