Instructions to use google/gemma-3-1b-pt with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use google/gemma-3-1b-pt with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="google/gemma-3-1b-pt")# Load model directly from transformers import AutoTokenizer, AutoModelForCausalLM tokenizer = AutoTokenizer.from_pretrained("google/gemma-3-1b-pt") model = AutoModelForCausalLM.from_pretrained("google/gemma-3-1b-pt") - Inference
- Notebooks
- Google Colab
- Kaggle
- Local Apps
- vLLM
How to use google/gemma-3-1b-pt with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "google/gemma-3-1b-pt" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "google/gemma-3-1b-pt", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'Use Docker
docker model run hf.co/google/gemma-3-1b-pt
- SGLang
How to use google/gemma-3-1b-pt with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "google/gemma-3-1b-pt" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "google/gemma-3-1b-pt", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "google/gemma-3-1b-pt" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "google/gemma-3-1b-pt", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }' - Docker Model Runner
How to use google/gemma-3-1b-pt with Docker Model Runner:
docker model run hf.co/google/gemma-3-1b-pt
Fine-tuned Gemma-3-1b model produces gibberish/empty output after quantization (GPTQ/AWQ/BitsAndBytes all fail)
Environment:
Model: google/gemma-3-1b-pt fine-tuned with Unsloth LoRA (r=8) trained with ChatML Format(as this is pretrained model)
Full precision model: Works perfectly, proper expected responses
Hardware: L40S 48GB VRAM
Issue:
After fine-tuning with Unsloth LoRA and merging weights, all quantization methods fail while the full precision model works perfectly.
Quantization Results:
AWQ (W4A16, W8A16): Produces repetitive gibberish loops and repeating endlessly)
GPTQ (W4A16, W8A8): Outputs all zeros immediately, no actual computation (returns in 20-30sec vs 1min for full precision model)
BitsAndBytes (4-bit, 8-bit): Gibberish output with repetition loops for 8bit and blank output for bit
All methods tried with/without ignore=["lm_head"]
Debugging Done:
Tested different generation parameters (temperature, repetition_penalty, sampling)
Tried various prompt formats (ChatML, simple text)
Verified model dtype shows torch.float16 even after "quantization" (suggesting silent failures)
Full precision model generates proper responses in ~1 minute
Are there quantization parameters specifically recommended for LoRA-merged models, or should quantization-aware training be used instead of post-training quantization for fine-tuned models?
Any guidance on successful quantization of fine-tuned Gemma models would be appreciated.
Thanks!
Hi,
Thanks for sharing the detailed description of your issue, Quantizing LoRA-merged models, especially large language models like google/gemma-3-1b-pt , can indeed be challenging due to several factors.
I recommend trying quantization-aware training (QAT) instead, which helps the model adapt during fine-tuning. Also, ensure you’re using quantization tools that explicitly support LoRA models (like the latest BitsAndBytes or GPTQ forks) . Hybrid approaches—keeping some layers in higher precision —can help too.
Kindly try and let me know if you have any concerns. Thank you.