Since 11th june i see 4 hours of cpu spike on the MA container (v2.9.1) which didnt exist before. I dont have a lot of music locally and it didnt change for weeks regarding size.
Seems to me the incremental detection is not working well and analysis starts on all files
I saw all the code changes on throtling cpu usage, but i guess here the root is in the mechanism beneath it. (or it's always using the full budget somehow)
anyone recognizing this?
The timeframe fits exactly with the background task schedule of audio analysis.
2026-06-17T00:00:00.121004556Z e[32m2026-06-17 00:00:00.120 INFO (MainThread) [music_assistant.audio_analysis] Background analysis (streaming): 270 track(s) pending across 2 provider(s); run budget 4.0he[0m
2026-06-17T01:33:05.474600170Z e[32m2026-06-17 01:33:05.474 INFO (MainThread) [music_assistant.Last.fm] Building Last.fm recommendationse[0m
2026-06-17T01:33:05.475120576Z e[32m2026-06-17 01:33:05.474 INFO (MainThread) [music_assistant.Last.fm] Last.fm recommendations built (0 folders)e[0m
2026-06-17T01:48:55.467965262Z e[32m2026-06-17 01:48:55.467 INFO (MainThread) [music_assistant.music.genre] Genre mapping scan completed: 0 items mapped (1.3s)e[0m
2026-06-17T01:48:57.104143850Z e[32m2026-06-17 01:48:57.103 INFO (MainThread) [music_assistant.music.genre] Genre mapping scan completed: 0 items mapped (1.6s)e[0m
2026-06-17T01:48:58.735743321Z e[32m2026-06-17 01:48:58.732 INFO (MainThread) [music_assistant.music.genre] Genre mapping scan completed: 0 items mapped (1.6s)e[0m
2026-06-17T03:26:38.458843857Z e[32m2026-06-17 03:26:38.458 INFO (MainThread) [music_assistant.audio_analysis] Background analysis: complete (270 candidates processed in 12398.3s)e[0m