git404hub

what is llm-inspector fr?

helasaoudi/llm-inspector — explained in plain English

Analysis updated 2026-05-18

22PythonAudience · ops devopsComplexity · 3/5LicenseSetup · moderate

tl;dr

A command line tool that shows exactly where GPU memory goes when running an LLM and projects how much quantization would save.

vibe map

mindmap
  root((llm-inspector))
    What it does
      GPU memory breakdown
      Quantization savings estimate
      Measured vs projected fields
    Tech stack
      Python
      PyTorch
      NVIDIA GPU
    Use cases
      Inspect running inference
      Estimate quantization savings
      Diagnose memory bottlenecks
    Audience
      ML engineers
      Infra operators

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Inspect a running Ollama or vLLM process to see exactly how GPU memory is split between weights, KV cache, and workspace.

VIBE 2

Estimate GPU memory savings from FP8 or AWQ quantization before applying them to a production model.

VIBE 3

Diagnose whether a memory bottleneck is caused by model weights or the KV cache to pick the right fix.

what's the stack?

PythonPyTorchCLINVIDIA GPU

how it stacks up fr

helasaoudi/llm-inspectoragno-agi/agent-platform-railwayalexantaluo0/acot-vla-wm
Stars222222
LanguagePythonPythonPython
Setup difficultymoderatemoderatehard
Complexity3/54/55/5
Audienceops devopsdeveloperresearcher

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires an NVIDIA GPU machine, deeper embedded metrics need the optional torch extra installed in the same environment as the model.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

in plain english

LLM Inspector is a command line tool that shows exactly what is happening inside a running AI model's memory on your GPU. Most monitoring tools tell you a process is using a certain amount of GPU memory, but not why. LLM Inspector breaks that number down into categories such as model weights, the KV cache, workspace memory, and other overhead, so you can see where every gigabyte is actually going. Beyond just showing current usage, it also projects what would happen if you applied different optimization strategies, starting with quantization, before you actually make any changes. For example, it can estimate how many gigabytes an FP8 or AWQ quantization scheme would save on model weights, and it will also tell you plainly when a technique will not help, such as noting that shrinking weights will not fix a bottleneck caused by a large KV cache. The README is clear that the live process, hardware, model, memory, and runtime numbers are measured directly, while the optimization projections are calculated estimates that never actually change the running model. It works with common inference setups including Ollama, vLLM, HuggingFace Transformers, FastAPI-based services, and custom PyTorch code, and runs on macOS, Linux, or any machine with an NVIDIA GPU, including DGX systems. A basic install through pip gives you the process level view, while installing the optional torch extra lets it attach directly inside the same Python environment as the model for deeper metrics like weights, KV cache, and activations. This is aimed at people who run or deploy large language models locally or on their own servers and want to understand and reduce GPU memory usage rather than guess at it. It is released under the MIT license.

prompts (copy fr)

prompt 1
Install llm-inspector and run it against my local Ollama process.
prompt 2
Explain the difference between measured and projected fields in llm-inspector's output.
prompt 3
Show me how to install the torch extra for deeper embedded metrics with llm-inspector.
prompt 4
Help me interpret an llm-inspector inspect output showing a large KV cache.

Frequently asked questions

what is llm-inspector fr?

A command line tool that shows exactly where GPU memory goes when running an LLM and projects how much quantization would save.

What language is llm-inspector written in?

Mainly Python. The stack also includes Python, PyTorch, CLI.

What license does llm-inspector use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is llm-inspector to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is llm-inspector for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.