Explore this comparison’s ranking

Comparison Counted

Which engine runs LFM2.5 1.2B Instruct best on M5 Max · 64 GiB?

Device
M5 Max · 64 GiB (Apple silicon Macs)
OS
macOS 27
Model
LFM2.5 1.2B Instruct, 1.2B parameters
Weights
bf16
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.

Which engine runs LFM2.5 1.2B Instruct best on M5 Max · 64 GiB? Ranked by Memory.
#EngineMemory and Decode
1Ollama, an approximate comparison, see details Ollama Memory: 2.45 GiB 197.6 tok/s decode
2llama.cpp, an approximate comparison, see details ggml-org Memory: 2.45 GiB 184.2 tok/s decode
3Magnitude, an approximate comparison, see details Magnitude Memory: 2.96 GiB 199.6 tok/s decode
4MLX LM, an approximate comparison, see details Apple (ml-explore) Memory: 3.26 GiB 198.3 tok/s decode
5Rapid-MLX, an approximate comparison, see details Rapid-MLX contributors Memory: 3.45 GiB 195.1 tok/s decode
6ZML, an approximate comparison, see details ZML Memory: 4.75 GiB 150.9 tok/s decode
details

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

Score: 100 is the best result in every comparison an engine entered; 80 is 80% of the best, on average. Only complete experiments with a passed output check count. How rankings work

† Ollama: approximate comparison. The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.

† llama.cpp: approximate comparison. The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.

† Magnitude: approximate comparison. The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default. Its phases were timed by the harness clock around the engine API, so they include transport that engine counters leave out.

† MLX LM: approximate comparison. The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.

† Rapid-MLX: approximate comparison. The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.

† ZML: approximate comparison. The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default. Its phases were timed by the harness clock around the engine API, so they include transport that engine counters leave out.

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
Ollama 0.40.13 · Metal · BF16 Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.197.6 range191.3–198.4136 range135–1382.45 range2.45–2.4515,385 range15,184–15,5336of 6 planned
llama.cpp b12110 · Metal · BF16 Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.184.2 range173.0–190.6142 range141–1442.45 range2.45–2.4514,523 range14,360–14,6596of 6 planned
Magnitude 0.2.17 · Metal · BF16 Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default. Its phases were timed by the harness clock around the engine API, so they include transport that engine counters leave out.199.6 range197.5–200.8113 range113–1192.96 range2.96–2.9618,058 range17,233–18,1136of 6 planned
MLX LM 0.32.2 · Metal · BF16 Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.198.3 range197.8–199.294.2 range93.9–95.03.26 range3.25–3.2621,872 range21,689–21,9566of 6 planned
Rapid-MLX 1.0.2 · Metal · BF16 Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default.195.1 range192.4–197.0100 range96.3–1023.45 range3.42–3.4620,564 range20,184–21,4306of 6 planned
ZML 20261106.0 · Metal · BF16 Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default. Its phases were timed by the harness clock around the engine API, so they include transport that engine counters leave out.150.9 range145.2–151.6130 range129–1304.75 range4.72–4.9415,773 range15,697–15,9016of 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.

Decode speed tok/s, higher is better
Time to first token ms, lower is better
Peak memory GiB, lower is better
Prefill speed tok/s, higher is better

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-m5-max-64gb--macos-27--lfm2.5-1.2b-instruct--bf16--archive-2048-128.