Instructions to use patdev/k3-a40-bootstrap with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use patdev/k3-a40-bootstrap with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf patdev/k3-a40-bootstrap:BF16 # Run inference directly in the terminal: llama cli -hf patdev/k3-a40-bootstrap:BF16
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf patdev/k3-a40-bootstrap:BF16 # Run inference directly in the terminal: llama cli -hf patdev/k3-a40-bootstrap:BF16
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 patdev/k3-a40-bootstrap:BF16 # Run inference directly in the terminal: ./llama-cli -hf patdev/k3-a40-bootstrap:BF16
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 patdev/k3-a40-bootstrap:BF16 # Run inference directly in the terminal: ./build/bin/llama-cli -hf patdev/k3-a40-bootstrap:BF16
Use Docker
docker model run hf.co/patdev/k3-a40-bootstrap:BF16
- LM Studio
- Jan
- Ollama
How to use patdev/k3-a40-bootstrap with Ollama:
ollama run hf.co/patdev/k3-a40-bootstrap:BF16
- Unsloth Desktop
- Docker Model Runner
How to use patdev/k3-a40-bootstrap with Docker Model Runner:
docker model run hf.co/patdev/k3-a40-bootstrap:BF16
- Lemonade
How to use patdev/k3-a40-bootstrap with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull patdev/k3-a40-bootstrap:BF16
Run and chat with the model
lemonade run user.k3-a40-bootstrap-BF16
List all available models
lemonade list
- Atomic Chat
Upload FINDINGS.md with huggingface_hub
Browse files- FINDINGS.md +13 -3
FINDINGS.md
CHANGED
|
@@ -48,9 +48,19 @@ by measurement:
|
|
| 48 |
|
| 49 |
What stands is empirical, not theoretical: **no rebalancing of CPU against GPU
|
| 50 |
within 92 GB of VRAM improves anything**, across placements spanning 60β88 GB of
|
| 51 |
-
VRAM and 4β33 GB of host traffic per token.
|
| 52 |
-
|
| 53 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 54 |
|
| 55 |
## What did NOT work, and why
|
| 56 |
|
|
|
|
| 48 |
|
| 49 |
What stands is empirical, not theoretical: **no rebalancing of CPU against GPU
|
| 50 |
within 92 GB of VRAM improves anything**, across placements spanning 60β88 GB of
|
| 51 |
+
VRAM and 4β33 GB of host traffic per token.
|
| 52 |
+
|
| 53 |
+
**The GPUs are not decorative, though β verified.** Running with `-ngl 0`, so
|
| 54 |
+
that essentially nothing sits in VRAM (1265 MiB and 269 MiB), gives **0.65
|
| 55 |
+
tok/s** against 2.51 for the same prompt with autofit. The two A40s are worth
|
| 56 |
+
**3.9Γ**. That check was run specifically because, if the GPUs had contributed
|
| 57 |
+
nothing, "buy more VRAM" would have been the wrong advice.
|
| 58 |
+
|
| 59 |
+
So the direction β fit more of the model in VRAM β is sound. The magnitude is
|
| 60 |
+
not predictable from here: a naive linear fit through (0 GB β 0.65) and
|
| 61 |
+
(92 GB β 2.94) lands near 5.4 tok/s at full residency, but removing the host
|
| 62 |
+
path entirely should be super-linear, since it swaps a mixed regime for pure
|
| 63 |
+
VRAM at 696 GB/s. The honest answer is "substantially better, number unknown".
|
| 64 |
|
| 65 |
## What did NOT work, and why
|
| 66 |
|