If you need a GUI, Unsloth Studio and LM Studio are both great frontends for llama.cpp. If you don't need a GUI, llama.cpp is the business for single-user deployments. Easy to use, always gets new model support very quickly, built-in Hugging Face client/cache support, works on probably everything (Mac, ROCm, CUDA, Vulkan, etc.).
replyI use llama.cpp w/ llama-swap
replyhttps://github.com/ggml-org/llama.cpp https://github.com/mostlygeek/llama-swap
FYI, llama-server can now be run in router mode so llama-swap is probably only needed for more exotic scenarios.
replyI’m using llama-swap because it can manage arbitrary backends, not just llama-server instances. I have llama.cpp chat and embedding models running alongside whisper-server all behind a single endpoint with per-model TTLs so they don't fight over the limited vram I have available on this box. Native routing could replace the llama.cpp part but not whisper so I guess I'm exotic ;)
replyI'm running it in router mode, but people on Reddit were recommending people use llama-swap instead. Am I missing something by using router mode?
replyI believe it's useful for running multiple llama.cpp forks at the same time (e.g. a model you want requires special patching)
replyThanks for the link to llama-swap. Didn’t know about it and will definitely install it.
replytry oMLX or vMLX - both great projects that offer some amazing performance optimizations for Apple Silicon that utilize UMA and NVME caching efficiently.
replyhttps://omlx.ai https://vmlx.net
That said, it's been a few weeks since I've looked so maybe llama.cpp has those features now... they really do move that quickly.
Jan is so much better.
replyThe link in that discussion has a section about that
replylm studio
reply