Instructions to use city96/t5-v1_1-xxl-encoder-gguf with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- llama-cpp-python
How to use city96/t5-v1_1-xxl-encoder-gguf with llama-cpp-python:
# !pip install llama-cpp-python from llama_cpp import Llama llm = Llama.from_pretrained( repo_id="city96/t5-v1_1-xxl-encoder-gguf", filename="t5-v1_1-xxl-encoder-Q3_K_L.gguf", )
output = llm( "Once upon a time,", max_tokens=512, echo=True ) print(output)
- Notebooks
- Google Colab
- Kaggle
- Local Apps
- llama.cpp
How to use city96/t5-v1_1-xxl-encoder-gguf with llama.cpp:
Install from brew
brew install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama-server -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M # Run inference directly in the terminal: llama-cli -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama-server -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M # Run inference directly in the terminal: llama-cli -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
Use Docker
docker model run hf.co/city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use city96/t5-v1_1-xxl-encoder-gguf with Ollama:
ollama run hf.co/city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
- Unsloth Studio new
How to use city96/t5-v1_1-xxl-encoder-gguf with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for city96/t5-v1_1-xxl-encoder-gguf to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for city96/t5-v1_1-xxl-encoder-gguf to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for city96/t5-v1_1-xxl-encoder-gguf to start chatting
- Docker Model Runner
How to use city96/t5-v1_1-xxl-encoder-gguf with Docker Model Runner:
docker model run hf.co/city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
- Lemonade
How to use city96/t5-v1_1-xxl-encoder-gguf with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull city96/t5-v1_1-xxl-encoder-gguf:Q4_K_M
Run and chat with the model
lemonade run user.t5-v1_1-xxl-encoder-gguf-Q4_K_M
List all available models
lemonade list
For the fastest inference on 12GB VRAM, are the following GGUF models appropriate to use?
Please if anyone can confirm or explain this:
Do the file size directly corresponds to the amount of VRAM that they will take up?
In order to have the fastest inference possible, is the goal to have all the models loaded within the GPU - VRAM itself?
1.) flux1-dev-Q4_K_S.gguf - 6.81 GB
2.) t5-v1_1-xxl-encoder-Q5_K_S.gguf - 3.29 GB
3.) clip_l.safetensors - 234 MB
Which make a total of about 10.5 GB.
Leaving 1-1.5GB VRAM as room for inference calculations.
Monitor is connected to iGPU and Browser's Hardware Acceleration has been turned off.
Same question here. And in the Model card they say at least use the Q5_K_M for the t5 encoder is that correct?
Actually, as long as every part is less than your vram, you can just load them in gpu one at a time. Yeah it will take extra time for load/unload, but with a ssd it's not too much.
Actually, as long as every part is less than your vram, you can just load them in gpu one at a time. Yeah it will take extra time for load/unload, but with a ssd it's not too much.
yeah i'm shocked to be generating 768p images in ~70s using flux dev on a 4gb graphics card