AppHalt Benchmark Lab · protocol v1.0

Measure first. Claim only what the data shows.

This public protocol defines how AppHalt tests app pausing: equal time windows, repeatable workloads, raw rows and explicit limits. It exists so future results can be checked rather than merely advertised.

Why publish an empty dataset template?

It fixes the reporting rules before results are known. That makes it harder to select only favorable numbers. It also gives reviewers the exact fields needed to reproduce or challenge a future AppHalt test.

Reproducible protocol

One comparison, six controls.

The core comparison is the same app and workload in three states: active but idle, paused with AppHalt, and resumed.

Record the environment

Log Mac model, chip, RAM, macOS, AppHalt version, tested app version, power source and starting battery level.

Define a fixed workload

Use the same open documents, tabs, project or call preparation in every run. Do not compare unrelated sessions.

Stabilize for five minutes

Let startup, indexing and initial network bursts settle. Record unusual system activity in the notes.

Measure for ten minutes

Capture average CPU and Energy Impact over the full window, plus memory allocation and system memory pressure.

Repeat at least three times

Alternate condition order where practical. Keep null, noisy and unfavorable runs rather than removing them silently.

Resume and verify

Confirm the app returns, note reconnections or interruptions, and report any workflow side effect alongside system metrics.

Metrics

What will and will not be measured.

MetricReasonInterpretation limit
Average CPU %Shows processor activity across the fixed intervalA single instant is not representative; processor percentages fluctuate
Average Energy ImpactApple’s relative indicator for current app energy useIt is not a direct battery-life percentage
App memory and memory pressureSeparates allocation from actual system memory stressPausing does not promise to free the app’s RAM
Workflow outcomeRecords reconnects, stopped transfers or other user-visible costsA lower metric is not useful if required work was interrupted
Battery level, only in long testsCan support a controlled laptop scenarioShort tests, screen brightness and wireless activity make broad claims unreliable

Planned evidence cases

Workflows selected for relevance, not spectacle.

These are registered test scenarios, not completed case-study results.

Battery focus session

Foreground: one document editor.
Background candidates: browser, chat and music apps left idle.
Report: CPU, Energy Impact, memory pressure and missed notifications after resume.

Video-call preparation

Foreground: a call app that remains excluded.
Background candidates: unrelated browser, creative and developer tools.
Report: system metrics plus call stability; never pause the active call app.

Developer focus

Foreground: editor and required local services remain active.
Background candidates: unrelated communication and design apps.
Report: metrics plus any affected watchers, servers or helper processes.

Publication rules

Rules applied before any result appears here.

All repetitions

Publish every valid run, not only the strongest result. Explain exclusions and preserve the original row.

No universal extrapolation

A result applies to the recorded Mac, app versions and workload. It does not become a guarantee for every user.

Product version attached

Every dataset identifies the AppHalt version and date so old evidence is not presented as current indefinitely.

Null results remain

If an idle app was already doing almost nothing, the pause may show little measurable difference. That outcome belongs in the dataset.

User cost reported

Reconnects, stopped notifications and interrupted tasks are reported next to performance metrics.

Corrections stay visible

Material changes receive a dated correction note rather than silently replacing the claim.

Evaluate it yourself

Test AppHalt on the workload that matters to you.

The public template lets you keep a comparable record instead of relying on a marketing percentage.

Download AppHalt Free

No guaranteed gain. Keep the result that your Mac actually shows.