RecipesSupplier
NVIDIA’s workstation playbooks
Browse serving, development and application guides.
For your deployment
Individual playbooks have their own hardware support matrices. Do not assume all target both platforms.
Help improve this record. Suggest a correction
ONPREMBENCH / GUIDES
What others figured out.
Ready to build on.
Technical recipes, operating lessons and real deployment experience. Start with your machine and keep the original authors in view.
Also in Guides: Operating lessons Shared setups
OperationsUnderstand Tech
Our journey from Ollama to vLLM to NIM
Why runtime selection became an operating decision at UT.
For your deployment
The narrative is operator-reported. Pinned versions and comparable results are still to be attached.
TroubleshootingUnderstand Tech
Investigating a 30-minute startup
Separate download, preparation, model loading and service readiness.
For your deployment
An open investigation, not a diagnosed universal NIM issue. Cold and warm starts need separate measurement.
OperationsUnderstand Tech
Offline is a property of the whole stack
Examine what still connects beyond the premises.
For your deployment
Distinguish initial installation, inference, application use, authentication and updates.
OperationsUnderstand Tech
Sharing one box across applications
An operator’s questions about memory and shared inference.
For your deployment
A model fitting in memory does not establish a supported-user count.
Deployment experienceUnderstand Tech
An execution agent beside the test equipment
Confidential Wi-Fi module test automation.
For your deployment
Exact hardware and proprietary test assets are not disclosed. This is an application field record.
Collected with context. Credit stays with the author.
We index and summarize original resources. Linked playbooks are not automatically tested by UT. Check the original version, licence and hardware matrix before using code. Historical forum reports keep their dates and resolution context.
Read the evidence policy