Direct answer
Establish a reference point for application memory by capturing measurements prior to loading, immediately after loading, during an active task, following cancellation, and after the application has been closed, without inferring any additional conditions beyond these specified checkpoints.
Evidence to collect
The claim becomes reviewable only when the following evidence is attached to the same artifact and test run:
- Metric definition
- Lifecycle checkpoints
- Repeated-run series
A device badge must come from an exact device, OS, artifact, runtime, backend, and workload record, not parameter-count intuition.
Implementation workflow
Connect the defined memory metric with the lifecycle checkpoints and a series of repeated runs, recording each value and comparing results across phases and trials to identify differences or consistencies in the collected evidence.
- Record the exact artifact and format.
- Measure the app before model load.
- Measure after model initialization.
- Run a representative product task.
- Repeat the fixed workload without restarting.
- Store failures, fallback, and cleanup behavior.
Failure patterns to prevent
- Using device free RAM as process memory
- Reporting one peak without phase
Avoid using the device's free RAM as a substitute for the application's own memory footprint, and avoid publishing conclusions based on a single peak value without separating and showing each phase as recorded evidence.
Minimum reproducibility record
| Layer | Record |
|---|---|
| Device | Manufacturer, model, chipset, RAM class, operating-system build |
| Software | Application version and git commit |
| Model | Family, variant, revision, format, file length, hash, quantization |
| Runtime | Name, revision, requested backend, observed backend evidence |
| Workload | Fixture revision, input hash, prompt hash, output policy |
| Outcome | Completed, failed, cancelled, fallback, and privacy-safe diagnostics |
Release checklist
- ☐ The primary query is answered without an unsupported number.
- ☐ Every artifact and runtime is pinned.
- ☐ The representative task and failure policy are explicit.
- ☐ Lifecycle, cancellation, cleanup, and fallback are tested.
- ☐ User-content and network boundaries are documented.
- ☐ Result wording applies only to the recorded configuration.
- ☐ The page links to raw method or evidence when results are added.
Sources and related evidence
Chinese deployment and troubleshooting content is organized in the .奇连 AI 端侧专题.