Explore this comparison’s ranking

Comparison Not counted

Which engine runs LFM2.5 350M best on OnePlus 13 · 16 GB?

Device
OnePlus 13 · 16 GB (Android phones)
OS
Android 16
Model
LFM2.5 350M, 350M parameters
Weights
4-bit
Workload
Archive 2048 input / 128 output: 2,048 tokens in, 128 out
Decoding
Greedy, batch 1, context 4,096
Power
Plugged in

Memory: Peak memory while generating: the less, the better.

Not counted: fewer than two scored engines. A comparison counts once two engines have scores for this objective. Its experiments are below, with their own numbers. How rankings work

Every experiment

Medians over valid trials, with the lowest and highest beneath. Eligible experiments are complete and passed their output check. The ranking above selects each engine's configuration for this objective when its required metrics are measured.

Every experiment in this comparison
ExperimentRanking eligibilityDecode tok/s, higher is betterFirst token ms, lower is betterMemory GiB, lower is betterPrefill tok/s, higher is betterValid trials
ExecuTorch 1.6.0 · CPU · 8da4w Complete Its output check failed: 5/8 of the checks the model passes at BF16; needs 7 and the mandatory ones (needle-start, needle-end). Left out, failed by every BF16 configuration: arithmetic, sort, word, continuation-128.121.4 range119.2–122.2Not measuredNot measured1,510 range1,503–1,5276of 6 planned
LiteRT-LM 0.19.0 · CPU · litert-int4 Complete Its output check failed: 6/8 of the checks the model passes at BF16; needs 7 and the mandatory ones (needle-start, needle-end). Left out, failed by every BF16 configuration: arithmetic, sort, word, continuation-128.92.8 range88.4–97.1Not measuredNot measured527.5 range526.1–530.46of 6 planned
llama.cpp b12110 · CPU · Q4_K_M Eligible, approximately: The experiments use different effective KV cache precision: fp32, litert-lm default, f16. The experiments here use different 4-bit schemes: 8da4w, litert-int4, Q4_K_M.133.3 range130.8–134.32,431 range2,385–2,499Not measured845.5 range822.9–861.86of 6 planned

Every trial, metric by metric

The line runs from an experiment's lowest to its highest valid trial, the dot is the median and each tick is one trial. Every scale starts at zero.

Caveats

  • Publisher cards identify the base model but do not always pin the exact export source checkpoint revision.
  • Engines may differ in quantization scheme, effective KV cache precision, kernels, and activations.

About this comparison

Worked out from its experiments: every experiment here shares the device, the OS major version, the power state, the base model, the quantization class and the workload. Measured under methodology v0.6. Comparison id glenn-oneplus-13--android-16--lfm2.5-350m--4-bit--archive-2048-128.