Collect path-specific measurements locally with documented timing and memory methods.
Host-owned measurement
The runtime does not gain hidden telemetry authority. The host chooses fields, clock, sampling interval, retention, privacy, and export.
Timing method
Record exactly when timing starts, what event counts as first token, whether prefill is included, how warm-up is handled, and which token count forms the throughput denominator.
Memory method
Name the source: process working set, private bytes, managed heap, operating-system resident set, GPU tool, or another method. Different methods are not interchangeable.
Evidence context
Retain package version, model hash, byte count, backend states, selected lane, environment summary, limits, stop reason, and known limitations with each result.
Available now
- The public UAIX.LmRuntime package family and canonical package documentation.
- The host-facing workflow and evidence distinctions described on this page.
Host responsibilities
- Select and trust inputs, define policy and limits, integrate the UI or service, retain application evidence, and test the exact deployment.
Not claimed
- A local timing record is not benchmark leadership.
- Telemetry fields must not contain private prompts or model paths by default.
Operational boundary
What this page covers: Collect path-specific measurements locally with documented timing and memory methods.
Available now: The documented package surfaces and this host-facing guidance are public.
Host responsibility: Own acquisition, trust, configuration, presentation, persistence, transport, policy, tests, and deployment.
Not claimed: Universal compatibility, production certification, safety certification, hidden fallbacks, or behavior beyond retained evidence.
Canonical sources: Canonical package documentation · Current release metadata
Last reviewed UTC:
Source and review record
Prerequisites
- Read Get Started
- Review host/runtime boundaries