Remove slower unit symbol cache

2026-07-16 18:18:39 +00:00
parent ea89e3bb6d
commit ab3e4dac2e
5 changed files with 6 additions and 44 deletions
@@ -15,8 +15,6 @@ Component resolution is divided into `component_path_us`, `component_artifact_us

 Successful first loads within the request are counted by `unit_load_count` and divided into `unit_module_us`, `unit_allocate_us`, `unit_import_us`, `unit_instantiate_us`, and `unit_initialize_us`. These cover compiled-module lookup, guest memory/table allocation, import construction, Wasmtime instantiation, and relocations/constructors/request binding. Repeated handlers from an already loaded unit are excluded.

-`unit_symbol_lookups` and `unit_symbol_cache_hits` count request-scoped import symbol resolution. Successful function and data resolutions are cached within one workspace; misses remain uncached so a later-loaded unit can satisfy them. The cache never crosses a request or Wasmtime Store.
-
 Wasm FastCGI workers retain up to `MYSQL_PERSISTENT_POOL_SIZE` credential-keyed MySQL connections (default `8`; set `0` to disable). UCE calls the client library's connection-reset operation before another request receives a cached connection, clearing transactions, temporary tables, session variables, and selected databases while avoiding a new authentication handshake. Same-request leases continue to share state until request cleanup.

 :example