-
Notifications
You must be signed in to change notification settings - Fork 0
Getting Started
Kritarth-Dandapat edited this page May 24, 2026
·
1 revision
This page covers installation, environment setup, and your first BitForge commands.
| Requirement | Version |
|---|---|
| Python | ≥ 3.8 |
| PyTorch | ≥ 2.1 |
| GPU (recommended) | CUDA-capable for quantization and eval |
BitForge targets consumer and workstation hardware. CPU-only runs are possible for small models and metric utilities, but GPTQ/AWQ calibration is GPU-bound in practice.
git clone https://github.com/Inference-Foundry/BitForge.git
cd BitForge
pip install -e .pip install -r requirements.txtCore dependencies include torch, transformers, accelerate, bitsandbytes, auto-gptq, autoawq, gguf, datasets, and click.
bitforge --helpExpected subcommands:
-
bitforge quantize— run quantization on a Hugging Face model -
bitforge evaluate— measure perplexity, latency, and memory
bitforge quantize \
--model-id meta-llama/Llama-2-7b-hf \
--bits 4 \
--method gptq \
--output-path ./artifacts/llama-2-7b-gptq-4bitSupported methods: ptq, gptq, awq, bitsandbytes. Supported bit widths: 2, 4, 8.
bitforge evaluate \
--model-id ./artifacts/llama-2-7b-gptq-4bit \
--dataset wikitext2 \
--device cudapython experiments/01_perplexity_benchmarks.pySee Experiments for the full list.
The site/ folder contains a static dashboard for exploring quantization trade-offs—no build step required.
cd site
python -m http.server 8080
# open http://localhost:8080Or open site/index.html directly in a browser. See Interactive Lab for details.
- VRAM: 4-bit quantization of a 7B model typically needs ~6–8 GB GPU memory during calibration; inference can run lower depending on runtime.
-
Apple Silicon: use
--device mpsfor evaluation where supported; some quant backends remain CUDA-only. - Disk: quantized artifacts and calibration caches can be several GB per model.
- Architecture — understand the package layout
- Quantization Theory — choose a method and bit width
- Runtime Integration — pick the right export format for your inference stack