I kept rewriting parameters every time I swapped models on vLLM and llama.cpp, so I built a tool to manage them (llmux, MIT)
Summary
A developer built llmux, an open-source tool to simplify managing model profiles across different engines like vLLM and llama.cpp, allowing one-click switching with Docker and NVIDIA GPU support.
Similar Articles
vllm-project/vllm v0.19.1
vLLM v0.19.1 release - a fast and easy-to-use open-source library for LLM inference and serving with state-of-the-art throughput, supporting 200+ model architectures and diverse hardware including NVIDIA/AMD GPUs and CPUs.
Is using vLLM actually worth it if you aren't serving the model to other people?
A user discusses the trade-offs between using vLLM and llama.cpp for local, single-user inference on AMD hardware, questioning if vLLM's performance benefits justify the complexity in non-enterprise settings.
llama.cpp is the linux of llm
The article draws a parallel between llama.cpp and Linux, positioning the open-source library as foundational infrastructure for running large language models.
llama.cpp now supports model management (downloading etc) via API
llama.cpp now supports model management including downloading and lifecycle management via its API, allowing full deployment without external tools.
ggml-org/llama.cpp
llama.cpp is an open-source C/C++ library for efficient LLM inference on local hardware, supporting various quantization methods and multiple backends (CPU, GPU, etc.).