Repository navigation
giq 0.5.3 — nothing kept warm by default
giq 0.5.3 changes one default: nothing is kept warm out of the box.
What changed
Until now three built-in recipes carried a residency priority: gemma-4-12b, whisper-large-v3 and ecapa-tdnn. A new install with their weights on disk kept about 14 GB loaded from its first boot, whether its operator wanted that or not. No built-in recipe pins anything now: a new install loads a model only when a job asks for it.
Keeping models warm is the operator's decision, made in one of three places:
config.yaml: list them underresidents:, in reload-priority order. The template shows an example.- The dashboard: set a recipe to keep warm in the Recipes view. That choice persists in
stats.db. - A recipe file of your own: set
residency.priority.
Upgrading
If you relied on the old default (gemma, whisper and ecapa loaded at boot without residents: in your config), add it explicitly before upgrading:
residents:
- gemma-4-12b
- whisper-large-v3
- ecapa-tdnnWhat's unaffected:
- Installs that already list
residents:. - Recipes pinned in the dashboard: a keep warm override still applies.
Full changelog: v0.5.2...v0.5.3