LMDeploy

Toolkit for compressing, deploying, and serving large language models with optimized inference.

Open SourceSelf HostedOffline CapableGPU Required
0.0 (0)

About

LMDeploy comes from the InternLM team as a toolkit for compressing, deploying, and serving large language models. It ships two inference engines: TurboMind, a high-performance CUDA engine with persistent batching, blocked KV cache, and optimized kernels, and a PyTorch engine aimed at flexibility and easier experimentation. Quantization support covers weight-only quantization and KV cache quantization, and the project reports up to 1.8 times higher request throughput than vLLM, with 4-bit inference running about 2.4 times faster than FP16. Coverage is broad: more than 40 LLM architectures including Llama, Qwen, DeepSeek, Gemma, and Phi, plus over 30 vision-language models such as InternVL, LLaVA, and Qwen-VL, spanning roughly 1B to 754B parameters. Multi-machine multi-GPU deployment, tensor parallelism, and automatic prefix caching round out the serving features. The toolkit is open source under Apache 2.0 and is used by teams putting LLM and VLM inference into production.

Should you use LMDeploy?

Pick it when

Pick LMDeploy when you serve vision-language models such as InternVL or Qwen-VL alongside LLMs on NVIDIA GPUs and want TurboMind's CUDA engine with 4-bit weight and KV cache quantization in one toolkit.

Look elsewhere when

Skip it if you want the widest architecture coverage and largest community, where vLLM leads, or the fastest structured JSON output, where SGLang specializes. Its throughput gains over vLLM are self-reported, so benchmark your workload.

Alternatives to LMDeploy

  • vLLM

    Broader model coverage and community, the default most tools integrate with, though LMDeploy reports higher throughput on TurboMind.

  • SGLang

    Strong structured output and prefix caching with AMD, TPU, and Ascend support, where LMDeploy's TurboMind engine is CUDA-focused.

  • TensorRT-LLM

    NVIDIA's own engine with FP8 and FP4 support and multi-node parallelism, tied to NVIDIA hardware and harder to set up.

  • LightLLM

    Pure Python stack that is easier to modify for scheduling research, where LMDeploy splits work between CUDA and PyTorch engines.

Reviews (0)

Leave a Review

No reviews yet. Be the first to review!