Browse the documentation

Early preview

Runtime cache

Interpreted and virtual-machine workloads (Python, JVM, Node.js) need their runtime and application files on disk. The Executor extracts them once into a deterministic, content-addressed cache and reuses the verified copy on every later start.

Where it lives

SettingLocation
Default~/.cache/oee/runtimes/<blake3-merkle-root>/
OverrideThe directory named by the environment variable OEE_CACHE_DIR

Each binary's segments 3 and 4 (the runtime and the application) are extracted into a directory named after the binary's BLAKE3 Merkle root. Two different builds never share a directory, and two copies of the same build always do.

How it behaves

  • Read-only while running. The extracted directory is locked with read-only permissions during execution, so the guest cannot change its own runtime.
  • Verified. The cache belongs to the Merkle root the supervisor has verified; a different build gets a different directory.
  • Clean host. Python runs with PYTHONHOME set to the extracted runtime and PYTHONNOUSERSITE=1; Node.js resolves modules inside the bundle. Nothing is installed globally, so no dependency conflicts with the host.
  • Kept after a stop. Stopping the application leaves the cache on disk, like the binary and your files.
  • Native binaries skip it. Go, Rust, C and C++ binaries have an empty runtime segment and launch from the verified runtime path, or from memfd on Linux when configured.

Startup

The startup figures are design targets, not measured results.

StartTarget overhead
Native Go or Rust binary, or warm-cached Python or JVM workloadLess than 15 ms
First run, with cold cache extractionUnder 350 ms

Pre-fetching runtimes at build time

The cache above is the run-time cache of a built binary. On the build machine, oee runtime list, oee runtime fetch and oee runtime verify list, pre-fetch and checksum-verify the portable CPython, jlink JDK and Node.js distributions that oee build bundles. See oee runtime.