Module 17: Pros, cons and limits · Lesson 17.5 · about 15 min
Limits in practice: setup, updates, heat and noise
The everyday costs of running AI yourself that nobody puts in the advert. Setup time, drivers and updates, heat, noise and battery, missing features like web search, and how to keep each small.
Module 17 · about 15 minutes · read first: 6.3 and 9.7. You’ll be able to plan for the hidden chores of local AI so they stay small.
1. Why this matters
Cloud AI is someone else’s job to keep running. Local AI is yours. None of these chores is hard, but together they are the main reason people give up on local setups. Planning for them is how you keep going.
It is a bicycle against the bus. The bike is cheaper and yours, but you pump the tyres.
2. The list
| Limit | What it looks like | Keep it small by |
|---|---|---|
| Setup time | An evening to a weekend the first time | Starting with LM Studio or Ollama (Module 9), not the most advanced engine |
| Updates | Engines update weekly, drivers monthly, models every few months | Updating on purpose, once a month, one thing at a time; writing down versions |
| Drivers | A graphics driver update breaks the engine | Keeping the last working driver installer; on Linux, holding the driver package |
| Heat | Fans, warm room, throttling | Airflow, a power limit on the card (Lesson 6.3) |
| Noise | A desktop at full fan in a quiet office | A Mac or AI box, or the machine in another room on the network (Lesson 15.4) |
| Battery | A laptop drains in an hour at full load | Plug in for long jobs; small models on battery |
| Missing features | No web search, phone app or sync out of the box | Add only what you need (Lesson 17.8) |
| Model churn | New models every month tempt you to switch | Switch only when a test on your tasks shows a real gain (Lesson 17.1) |
| Disk space | Models of 5 to 70 GB each pile up | ollama rm or deleting old files; keep two or three models |
A driver is the small program that lets the operating system talk to the graphics card. A rollback means going back to the last version that worked.
Friday night. A dental clinic's AI machine works fine. Overnight, Windows installs a new graphics driver on its own.
Monday morning. The engine will not start: the new driver does not match the engine's version. Nobody changed anything on purpose.
Roll back. The clinic reinstalls the last working driver from the installer they kept. The engine starts again in ten minutes.
Make it a routine. They stop automatic driver installs and put "AI machine updates" in the calendar for the first Friday of each month: note versions, update one thing, test three saved prompts. No more surprise Mondays.
Maths and principle
Principle: chores are a cost; count them in hours.
Equation: yearly upkeep hours ≈ setup + 12 × monthly update time + fixes. Multiply by your hourly value for Lesson 16.3.
Analogy: a bicycle against the bus. The bike is cheaper and yours, but you pump the tyres.
Try it: 6 hours setup, 1 hour a month updates, 4 hours of fixes a year? (6 + 12 + 4 = 22 hours in the first year.)
- hsetup
- hours to get it working the first time: an evening to a weekend
- hmonth
- hours a month for planned updates and tests
- hfixes
- hours a year fixing things that broke
- Physical meaning
- This is the part of the price you pay in time instead of money. A monthly routine keeps hfixes small, because one planned change at a time is easy to undo; many surprise changes at once are not.
“Once it is set up, it just keeps working.” Drivers, engines and the operating system keep changing underneath, and the most common cause of a broken setup is an update nobody chose. Update on purpose, one thing at a time, and keep the last working installer.
3. Worked example
Made-up office. A dental clinic’s AI machine stopped working one Monday after Windows installed a new graphics driver overnight. Fix: roll back the driver, then set Windows to stop installing drivers automatically, and put “AI machine updates” in the calendar for the first Friday of each month. No more surprise Mondays.
4. Practice
- Which three chores in the table would affect you most?
- Write a one-line monthly update routine for your machine.
- How many models do you really need on disk?
Answers
- Your answer.
- For example: “First Friday: note versions, update engine, test three saved prompts; update drivers only if needed.”
- Usually two or three: a fast small one, a strong everyday one, maybe one special-purpose model.
New words: driver, rollback, model churn, upkeep.
- The chores: setup, updates, drivers, heat, noise, battery, missing features, model churn and disk space.
- Most breakages come from updates nobody chose: update once a month, one thing at a time, and write down versions.
- Keep the last working driver installer so you can roll back in minutes.
- Count upkeep in hours (setup + 12 × monthly + fixes) and add it to the cost of owning.
Check yourself
Sources
- Lessons 6.3 (cooling and noise), 6.4 (laptops and throttling), 9.7 (troubleshooting) of this course
- NVIDIA driver release notes and CUDA compatibility (official page), https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/
- Ollama documentation (installing, updating, listing and removing models), https://docs.ollama.com
Your ticks stay in this browser. Save them as a file on the course home.
Updated 2026-11-22. Prices and model names change fast: check the official source before you buy.