+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Drivers / Frameworks / Toolkits (https://www.datasculpting.ai/inference/forumdisplay.php?fid=8)
+--- Forum: Apple / MLX (https://www.datasculpting.ai/inference/forumdisplay.php?fid=33)
+--- Thread: Apple unified memory limits with vLLM (/showthread.php?tid=825)
Pages:
1
2
Re: Apple unified memory limits with vLLM - visionyard23 - 10-13-2026
Quote:I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at VRAM headroom. Once you
I don't think that's the whole story. I've seen people blame continuous batching when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Re: Apple unified memory limits with vLLM - dockridge - 10-13-2026
Tried to reproduce it just now. On mini PC with llama.cpp, I saw basically the same behavior.
Re: Apple unified memory limits with vLLM - mlxgarden - 10-13-2026
What exact setup are you running? What model, what runtime, and roughly what context size?
Re: Apple unified memory limits with vLLM - sanescope - 10-14-2026
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.