music-assistant: raise memory limit to 6Gi so Smart Fades can load #46

Merged
k.renner merged 1 commits from worktree-ma-smart-fades-ram into master 2026-06-26 11:36:03 +00:00
Owner

Problem

The Smart Fades audio-analysis provider (new in MA 2.9) shows 'This provider requires attention' / RECONFIGURE in the UI. Verified root cause from the live pod log:

WARNING [music_assistant] Provider(instance) Smart Fades can not run on this
system: at least 4GB of RAM is required (2.0GB detected).

Smart Fades loads an ML model and gates startup on the pod's cgroup memory limit, currently 2Gi. Loudness Analysis (lightweight) is unaffected. CPU/AVX2 (x86-64-v3) and the 2-core minimum are already met -- RAM is the sole blocker.

Fix

Raise pod memory limit 2Gi -> 6Gi (request 512Mi -> 1Gi). Upstream recommends 6GB+ and warns the 4GB minimum risks OOM under load, so this uses the recommended value rather than the bare floor. k8s-edge is a 12GB VM currently using ~4GB (~7GB free). On next Flux reconcile the pod restarts (Recreate, brief MA blip) and Smart Fades passes the requirement check.

Optional follow-ups

  • Node headroom: HA(8Gi)+MA(6Gi) on a 12GB VM is limits-overcommit (real usage far lower). If OOM appears, bump the VM 12->16GB in opentofu/vm_153_k8s_edge.tf (needs edge-node reboot).
  • CPU cores: 2-core minimum met; upstream recommends 4 for best experience (faster analysis, not required) -- also a VM change + reboot.

Generated with Claude Code

## Problem The Smart Fades audio-analysis provider (new in MA 2.9) shows 'This provider requires attention' / RECONFIGURE in the UI. Verified root cause from the live pod log: WARNING [music_assistant] Provider(instance) Smart Fades can not run on this system: at least 4GB of RAM is required (2.0GB detected). Smart Fades loads an ML model and gates startup on the pod's cgroup memory limit, currently 2Gi. Loudness Analysis (lightweight) is unaffected. CPU/AVX2 (x86-64-v3) and the 2-core minimum are already met -- RAM is the sole blocker. ## Fix Raise pod memory limit 2Gi -> 6Gi (request 512Mi -> 1Gi). Upstream recommends 6GB+ and warns the 4GB minimum risks OOM under load, so this uses the recommended value rather than the bare floor. k8s-edge is a 12GB VM currently using ~4GB (~7GB free). On next Flux reconcile the pod restarts (Recreate, brief MA blip) and Smart Fades passes the requirement check. ## Optional follow-ups - Node headroom: HA(8Gi)+MA(6Gi) on a 12GB VM is limits-overcommit (real usage far lower). If OOM appears, bump the VM 12->16GB in opentofu/vm_153_k8s_edge.tf (needs edge-node reboot). - CPU cores: 2-core minimum met; upstream recommends 4 for best experience (faster analysis, not required) -- also a VM change + reboot. Generated with Claude Code
k.renner added 1 commit 2026-06-26 10:49:31 +00:00
The Smart Fades audio-analysis provider added in MA 2.9 loads an ML model
and reads the pod cgroup memory limit to gate startup. At the current 2Gi
limit it refuses to run:

  Provider(instance) Smart Fades can not run on this system: at least 4GB
  of RAM is required (2.0GB detected).

so the provider shows 'requires attention' / RECONFIGURE in the UI.
Loudness Analysis (lightweight) is unaffected. CPU/AVX2 (x86-64-v3) and the
2-core minimum are already met; RAM is the sole blocker.

Upstream recommends 6GB+ and warns the 4GB minimum risks OOM under load.
k8s-edge is a 12GB VM currently using ~4GB, so set the limit to the
recommended 6Gi (request bumped 512Mi->1Gi). On next reconcile MA restarts
and Smart Fades passes the requirement check.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
k.renner merged commit 68e175df79 into master 2026-06-26 11:36:03 +00:00
Sign in to join this conversation.