██╗   ██╗██╗██████╗ ███████╗███╗   ███╗██╗     ██╗  ██╗
██║   ██║██║██╔══██╗██╔════╝████╗ ████║██║     ╚██╗██╔╝
██║   ██║██║██████╔╝█████╗  ██╔████╔██║██║      ╚███╔╝ 
╚██╗ ██╔╝██║██╔══██╗██╔══╝  ██║╚██╔╝██║██║      ██╔██╗ 
 ╚████╔╝ ██║██████╔╝███████╗██║ ╚═╝ ██║███████╗██╔╝ ██╗
  ╚═══╝  ╚═╝╚═════╝ ╚══════╝╚═╝     ╚═╝╚══════╝╚═╝  ╚═╝

The Numbers Don't Lie

Real benchmarks. Real hardware. No asterisks.

Models
34
Avg Decode
158.7
tok/s
Avg Prefill
87.7
tok/s
Avg TTFT
44
ms

Where It Really Matters

When you send a message and wait for the AI to respond, TTFT determines how long you stare at a blank screen. This is the metric that makes or breaks conversational UX.

ModelVibeMLXmlx-engineSpeedup
TinyMistral-248M3.6ms117ms32×
QwQ-0.5B4.8ms228ms47×
DeepSeek-R1-1.5B5.9ms389ms66×
Llama-3.2-1B14.4ms271ms19×
Mistral-7B-v0.320.3ms1,283ms63×
Phi-3-mini11.1ms737ms66×
Qwen2.5-Coder-3B11.2ms638ms57×

Why the massive difference? VibeMLX compiles directly into the application. No Python interpreter. No cross-language FFI overhead. No framework abstraction layers. The moment your prompt is ready, tokens start flowing.

Test System: Apple M3 Max | 16 cores | 128GB Unified Memory

Bundle & Resource Comparison

How Vibe Mode compares to popular AI coding assistants.

MetricVibe ModeOther Tools*
Download Size100 MB1,000+ MB
Memory at Idle< 100 MB3-5 GB
Time to Launch< 1 sec3-8 seconds
FrameworkSwiftUIElectron
InferenceNativeSubprocess
TerminalGhosttyxterm.js
DependenciesZeronode_modules

* Measured against popular AI coding assistants. We're not naming names, but you know who. If you want specifics, ask in Discord.

How We Test

  • •All tests on Apple M3 Max (128GB unified memory)
  • •Each model tested 3+ times, results averaged
  • •Prefill: 40-token prompts
  • •Decode: 100-token generations
  • •Models loaded fresh for fair comparison
  • •Background processes killed before testing
  • •Memory cleared between tests

Benchmarks are reproducible. Code available on request.