Explore this comparison’s ranking

Comparison Counted

Which engine runs LFM2.5 350M best on M5 Max · 64 GiB?

Device
M5 Max · 64 GiB (Apple silicon Macs)
OS
macOS 27
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

Speed: Decode speed: tokens generated per second.

Which engine runs LFM2.5 350M best on M5 Max · 64 GiB? Ranked by Speed.
#EngineDecode and First token
1Rapid-MLX, an approximate comparison, see details Rapid-MLX contributors Decode: 946.8 tok/s 57.6 ms first token
2MLX LM, an approximate comparison, see details Apple (ml-explore) Decode: 897.8 tok/s 56.2 ms first token
3Magnitude, an approximate comparison, see details Magnitude Decode: 884.9 tok/s 46.5 ms first token
4Ollama, an approximate comparison, see details Ollama Decode: 700.6 tok/s 64.1 ms first token
5llama.cpp, an approximate comparison, see details ggml-org Decode: 650.0 tok/s 65.2 ms first token
Not ranked in this view
Not rankeduzu Mirai Failed Failed in 1 comparison. No trial was valid.
Not rankedExecuTorch PyTorch (Meta) Not counted 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.
Not rankedLiteRT-LM Google AI Edge Not counted 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.
details

Speed Decode speed: tokens generated per second.

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

† Rapid-MLX: approximate comparison. The experiments use different effective KV cache precision: bf16, fp32, litert-lm default, f16, magnitude default, model-dtype. Its weights are 4-bit in another scheme: mlx-affine-4bit-g64, where most use Q4_K_M.

† MLX LM: approximate comparison. The experiments use different effective KV cache precision: bf16, fp32, litert-lm default, f16, magnitude default, model-dtype. Its weights are 4-bit in another scheme: mlx-affine-4bit-g64, where most use Q4_K_M.

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

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

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

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
Rapid-MLX 1.0.2 · Metal · mlx-affine-4bit-g64 Eligible, approximately: The experiments use different effective KV cache precision: bf16, fp32, litert-lm default, f16, magnitude default, model-dtype. Its weights are 4-bit in another scheme: mlx-affine-4bit-g64, where most use Q4_K_M.946.8 range941.4–949.557.6 range55.2–57.91.83 range1.58–2.1735,995 range35,755–37,4896of 6 planned
MLX LM 0.32.2 · Metal · mlx-affine-4bit-g64 Eligible, approximately: The experiments use different effective KV cache precision: bf16, fp32, litert-lm default, f16, magnitude default, model-dtype. Its weights are 4-bit in another scheme: mlx-affine-4bit-g64, where most use Q4_K_M.897.8 range894.8–901.256.2 range46.9–56.81.78 range0.79–2.1636,803 range36,471–44,2556of 6 planned
Magnitude 0.2.17 · Metal · Q4_K_M Eligible, approximately: The experiments use different effective KV cache precision: bf16, fp32, litert-lm default, f16, magnitude default, model-dtype. Its phases were timed by the harness clock around the engine API, so they include transport that engine counters leave out.884.9 range879.3–906.646.5 range46.3–49.11.05 range1.05–1.0644,058 range41,750–44,2666of 6 planned
Ollama 0.40.13 · Metal · Q4_K_M Eligible, approximately: The experiments use different effective KV cache precision: bf16, fp32, litert-lm default, f16, magnitude default, model-dtype.700.6 range693.0–726.664.1 range54.1–64.40.47 range0.47–0.4733,581 range33,462–39,9796of 6 planned
llama.cpp b12110 · Metal · Q4_K_M Eligible, approximately: The experiments use different effective KV cache precision: bf16, fp32, litert-lm default, f16, magnitude default, model-dtype.650.0 range639.9–689.265.2 range54.5–70.80.47 range0.47–0.4731,928 range29,289–38,4666of 6 planned
ExecuTorch 1.6.0 · Metal · mlx-4w-g64 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.738.4 range725.7–747.1107 range107–107Not measured19,140 range19,140–19,3216of 6 planned
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.246.8 range237.4–248.5720 range719–725Not measured2,844 range2,829–2,8486of 6 planned
LiteRT-LM 0.19.1 · 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.184.6 range181.0–185.31,499 range1,498–1,5071.09 range1.09–1.101,382 range1,374–1,3836of 6 planned
uzu 0.6.17 · Metal · mirai-m Failed No trial was valid.Not measuredNot measuredNot measuredNot measured0of 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-350m--4-bit--archive-2048-128.