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
- bf16
- Workload
- Archive 2048 input / 128 output: 2,048 tokens in, 128 out
- Decoding
- Greedy, batch 1, context 4,096
- Power
- Plugged in
Ranking
Memory: Peak memory while generating: the less, the better.
| # | Engine | Memory and Decode |
|---|---|---|
| 1 | Ollama†, an approximate comparison, see details | Memory: 0.92 GiB 469.0 tok/s decode |
| 2 | llama.cpp†, an approximate comparison, see details | Memory: 0.92 GiB 442.7 tok/s decode |
| 3 | MLX LM†, an approximate comparison, see details | Memory: 1.01 GiB 526.9 tok/s decode |
| 4 | Rapid-MLX†, an approximate comparison, see details | Memory: 1.28 GiB 532.2 tok/s decode |
| 5 | Magnitude†, an approximate comparison, see details | Memory: 1.35 GiB 510.1 tok/s decode |
| 6 | ZML†, an approximate comparison, see details | Memory: 4.87 GiB 261.0 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.
† 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.
† 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.
† 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.
| Experiment | Ranking eligibility | Decode tok/s, higher is better | First token ms, lower is better | Memory GiB, lower is better | Prefill tok/s, higher is better | Valid trials |
|---|---|---|---|---|---|---|
| Ollama 0.40.13 · Metal · BF16 | Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default. | 469.0 range429.0–473.7 | 63.4 range63.2–63.5 | 0.92 range0.91–0.92 | 33,834 range33,703–33,880 | 6of 6 planned |
| llama.cpp b12110 · Metal · BF16 | Eligible, approximately: The experiments use different effective KV cache precision: f16, magnitude default, model-dtype, zml default. | 442.7 range427.3–456.7 | 66.2 range63.9–69.3 | 0.92 range0.92–0.92 | 31,446 range29,964–32,683 | 6of 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. | 526.9 range526.0–529.1 | 38.7 range30.4–38.8 | 1.01 range0.99–1.01 | 53,685 range53,568–68,746 | 6of 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. | 532.2 range526.9–535.6 | 46.9 range45.9–49.3 | 1.28 range1.27–1.33 | 44,254 range42,124–45,258 | 6of 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. | 510.1 range491.6–519.0 | 48.9 range48.7–49.0 | 1.35 range1.34–1.35 | 41,885 range41,783–42,028 | 6of 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. | 261.0 range259.0–263.3 | 59.6 range59.2–60.2 | 4.87 range4.74–4.91 | 34,342 range34,045–34,575 | 6of 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-m5-max-64gb--macos-27--lfm2.5-350m--bf16--archive-2048-128.