llamaperf

mlx-serve

An inference engine for running open-weight LLMs locally.

10 community reports

This engine doesn't yet have an editorial profile on llamaperf. The community reports below show how it's been used in practice across different hardware.

Top GPUs running mlx-serve

GPUVRAMReportsMedian t/s, Qwen3.8 125B · 6B active 3-bit
M4 Max 128GBapple128GB2no plain run of this model
M5 Max 128GBapple128GB2no plain run of this model
M5 Ultra 96GBapple96GB2no plain run of this model
M2 Max 96GBapple96GB1no plain run of this model
M3 Ultra 256GBapple256GB1no plain run of this model
M4 Max 64GBapple64GB152.6
M5 Ultra 256GBapple256GB1no plain run of this model

mlx-serve against other engines

Pairs of plain runs on the same card, of the same model size at the same bit class: one device, one request, no speculative decoding, the whole model in memory. Context length and build still differ between the two sides, and each side shows its own.

No matched pair yet. No card has plain runs of one model size at one bit class on mlx-serve and on another engine, so llamaperf can't say how it compares on speed. Add a run.

mlx-serve results by GPU

Every card people have run mlx-serve on, with each report's model, quant and speed, newest first. Runs on several cards, with speculative decoding, with batched requests or with part of the model in system RAM say so, since each describes a different setup.

mlx-serve on M5 Max 128GB2 reports

mlx-serve on M5 Ultra 96GB2 reports

mlx-serve on M2 Max 96GB1 report

mlx-serve on M5 Ultra 256GB1 report

Top models on mlx-serve

Frequently asked

Is mlx-serve faster than other engines?

llamaperf has no matched comparison for mlx-serve yet: no card has plain runs of the same model size at the same bit class on mlx-serve and on another engine. Speed claims about engines need that pairing, so this page doesn't make one.