In this article
The GTX 1060 name does not establish capacity or memory type; verify 3/5/6 GB and GDDR5X using specific primary board specifications.
One profile with explicit AIB variants
Do not record every GTX 1060 as one 6 GB configuration. The table covers verified 3/5/6 GB GDDR5 boards, a specific GIGABYTE 6 GB GDDR5X board and a 9 Gbps GDDR5 revision. Capacity belongs to one GPU. The 120 W values are tied to listed sources; power for the GIGABYTE board is not reliably established here and remains unknown. Do not transfer another MSI board’s figure. Smaller variants support identification and limitations rather than a broad LLM serving promise.
| Official variant | Memory per GPU | Memory type | Board power | Evidence |
|---|---|---|---|---|
| NVIDIA GeForce GTX 1060 — 6 GB GDDR5 8 Gbps reference | 6 GB | GDDR5 | 120 W | Specification |
| NVIDIA GeForce GTX 1060 — 6 GB GDDR5 9 Gbps MSI GAMING+ 6G | 6 GB | GDDR5 | 120 W | Specification |
| NVIDIA GeForce GTX 1060 — 6 GB GDDR5X GIGABYTE GV-N1060WF3OC-6GD | 6 GB | GDDR5X | Not verified | Specification |
| NVIDIA GeForce GTX 1060 — 5 GB GDDR5 MSI regional 5G | 5 GB | GDDR5 | 120 W | Specification |
| NVIDIA GeForce GTX 1060 — 3 GB GDDR5 MSI 3G OC | 3 GB | GDDR5 | 120 W | Specification |
Conditional Pascal inference
NVIDIA lists CC 6.1, below the current vLLM floor of 7.5, so that backend’s support is not claimed. For llama.cpp CUDA, pin commit, GGUF, target and offload. CUDA 13 removes pre-7.5 offline compilation, requiring a compatible legacy build such as suitable CUDA 12 and driver. A bounded request checks actual placement, answer and completion. A smaller file guarantees neither runtime nor KV headroom. Keep CPU-only results distinct from GPU or hybrid execution, preserving the actual configuration.
Use a real Cycles scene
Blender 5.2 documents CUDA CC 5.0 and OptiX conditions including driver 575 or newer. Pascal clears the general floor with a suitable build/driver and detection. The 1060 lacks RTX RT cores, which does not automatically prohibit every OptiX path. Preserve a small project, assets and backend for the actual board, then inspect image and memory. Host RAM involvement does not expand local GB. Another renderer needs its own requirements; success promises no arbitrary scene fit. Keep the project package and execution evidence together.
Bind the worker to board evidence
The registry contains exact AIB SKU, capacity/type, driver and binary target. Do not infer GDDR5X from observed speed or fill unknown power with another board’s value. GDDR5X alone is not a measured advantage. Verify actual connectors, cooling and host resources, especially during offload. Confirm VRAM ownership release before queue handover. Normal validation requires neither forced clocks nor disabled protections. Those actions cannot correct faulty inventory, which should be resolved before admitting new jobs. Preserve original sources alongside any normalized fields so later audits can reproduce the classification.
Preserve family identification evidence
The package contains raw source, AIB identity, LLM and scene manifests, settings and outcomes. If a card is 3 or 5 GB instead of an assumed 6 GB, correct classification and redefine its budget. Unsupported operations point to build, while memory pressure points to footprint and offload. The conclusion concerns a specific GTX 1060 and verified legacy path. It promises neither current vLLM nor TPS, universal fit or equal behavior across variants. An explicit table preserves useful equipment history without invented specifications or confusing the GPU name with every board implementation.
llama.cpp GPU layers: verify partial model offloading · Build a GPU Inventory CSV with nvidia-smi · GPU catalog