hpx cache#
Manage local caches used by hpx and its NSX build dependency.
Synopsis#
Description#
hpx caches NSX module artifacts, git-artifact content hashes, resolved refs, and generated firmware workspaces between runs so repeat profiles avoid network fetches and full rebuilds.
Profiles sharing a work directory run one at a time, from engine preparation
through profile and power capture and report generation. A second profile waits
until the first releases the directory. --clean also waits before clearing
cached contents. Use distinct --work-dir paths for concurrent profiles on
separate probes.
hpx cache info— show the cache location and disk usage.hpx cache purge— remove all NSX persistent cache items (module artifacts, legacy/v1/v2 git-artifact hash files and their lock sidecars, and resolved refs) through the neuralSPOT-X cache API, plus generated HPX workspaces. Unrelated files underNSX_CACHE_DIRare preserved. The next run re-fetches, re-hashes, and rebuilds everything from scratch.
When to purge#
- To force a fresh resolve of NSX module dependencies (e.g. to pick up a fix newly merged to a tracked branch).
- To reclaim disk space.
- To rule out stale build state when debugging.
For fast repeat builds with a verified, frozen module tree, see the
--offline flag on hpx profile (--frozen is a
deprecated alias).