Explore this comparison’s ranking

Comparison Counted

Which engine runs Ternary Bonsai 2 27B best on M5 Max · 64 GiB?

Device
M5 Max · 64 GiB (Apple silicon Macs)
OS
macOS 27
Model
Ternary Bonsai 2 27B, 27B parameters
Weights
2-bit
Workload
Archive 256 input / 128 output: 256 tokens in, 128 out
Decoding
Greedy, batch 1, context 4,096
Power
Plugged in

Balanced: Decode speed, time to first token and peak memory, weighted equally.

Which engine runs Ternary Bonsai 2 27B best on M5 Max · 64 GiB? Ranked by Balanced.
#EngineBalanced score out of 100
1Ollama, an approximate comparison, see details Ollama 100 /100 Balanced score
2llama.cpp, an approximate comparison, see details ggml-org 98 /100 Balanced score
3MLX LM, an approximate comparison, see details Apple (ml-explore) 90 /100 Balanced score
Not ranked in this view
Not rankedMagnitude Magnitude Unsupported Unsupported in 1 comparison. Magnitude 0.2.17 reports this GGUF as Unsupported (magnitude catalog inspect)
details

Balanced Decode speed, time to first token and peak memory, weighted equally.

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, model-dtype.

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

† MLX LM: approximate comparison. The experiments use different effective KV cache precision: f16, model-dtype. Its weights are 2-bit in another scheme: mlx-affine-2bit-g128, where most use Q2_0.

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 · Q2_0 Eligible, approximately: The experiments use different effective KV cache precision: f16, model-dtype.45.1 range45.0–45.2375 range374–3857.94 range7.94–8.12685.8 range667.3–687.06of 6 planned
llama.cpp b12110 · Metal · Q2_0 Eligible, approximately: The experiments use different effective KV cache precision: f16, model-dtype.43.2 range40.8–43.5384 range382–4077.94 range7.94–8.12668.1 range630.7–670.86of 6 planned
MLX LM 0.32.2 · Metal · mlx-affine-2bit-g128 Eligible, approximately: The experiments use different effective KV cache precision: f16, model-dtype. Its weights are 2-bit in another scheme: mlx-affine-2bit-g128, where most use Q2_0.45.3 range44.4–45.3421 range419–4939.65 range9.64–9.65609.2 range520.6–612.76of 6 planned
Magnitude 0.2.17 · Metal · Q2_0 Unsupported Magnitude 0.2.17 reports this GGUF as Unsupported (magnitude catalog inspect)––––0of 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--ternary-bonsai-2-27b--2-bit--archive-256-128.