Skip to content

Memtrace v1.1.10

Choose a tag to compare

View all tags
@Alex793x Alex793x released this 03 Sep 11:33
· 51 commits to main since this release
v1.1.10
27da025

Memtrace v1.1.10

The 1.1.9 CPU governor is opt-in

New

  • New features land on Nightly first: npm install -g memtrace@nightly is the same memtrace command, and it is not always stable. They still ship on the default install. memtrace install stays on the channel you already have.

Changed

  • The CPU governor introduced in 1.1.9 is now opt-in (MEMTRACE_CPU_GOVERNOR=on). On by default it budgeted background work to half the performance cores and a quarter on battery, moved indexing and embedding threads to efficiency cores, and parked work its watchdog judged idle; on a busy laptop that read as memtrace start and memtrace index doing nothing. 1.1.10 schedules exactly as 1.1.8 did. The restart fixes that made 1.1.9 cheap to leave running (a checkpoint and vector-index recovery proportional to what changed, no re-embedding on restart) do not depend on the governor and stay on.
  • The database sidecar runs at normal scheduling priority again. 1.1.9 started it one notch below normal (MEMTRACE_SIDECAR_PRIORITY=low brings that back), which made every query wait behind whatever else a loaded machine was running.

Fixed

  • Sidecars are always closed by memtrace stop and by Ctrl-C, on every platform. On macOS the Cortex daemon (memcortex-daemon) kept running and burning CPU after memtrace stop and after Ctrl-C: the stop command matched sidecars to a workspace by a --data-dir argument that the Cortex daemon does not use, and macOS ties no child to its parent the way Windows job objects and Linux parent-death signals do. Every owner now records each sidecar it spawns in a ledger next to its pid file, and memtrace stop, the owner's own shutdown and signal paths, the next owner's start, and memtrace doctor --fix close whatever that ledger names, with a hard kill after three seconds; a recycled pid is never touched.
  • The 1.1.9 check for symbols that already have a vector is now limited to 5 seconds per repository (MEMTRACE_EMBED_PRESENCE_SCAN_SECS; 0 disables it); past that the pass embeds from cache as before, and its duration is logged. MEMTRACE_FORCE_EMBED=1 re-embeds everything.
  • Windows: a workspace owner started from an elevated terminal, or any process the current user may not open, is no longer treated as dead. Attaching sessions tried to take over its store and reported the store as locked.

Install

npm install -g memtrace
Assets 4
Loading