Limiting Beet (OOM crash)

[IngwiePhoenix]

[81437.188916] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=beet,pid=6366,uid=0
[81437.188967] Out of memory: Killed process 6366 (beet) total-vm:5441296kB, anon-rss:5382208kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:10688kB oom_score_adj:0
[81437.633603] oom_reaper: reaped process 6366 (beet), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

Looks like it went quite hard. Any way I can limit it, to some degree? This was during a quiet import. I did see the threaded option, but as far as I can tell, its either yes or no, I can't just limit it to 2 or 4 threads (i have 8 cores in total).

[sampsyo]

The threaded beets importer uses as many threads as it has import stages. Typically, these are not too memory-hungry by themselves…

Which plugins are you using? It could be that one of them is the culprit, especially if it has to do with audio processing (e.g., ReplayGain or Chromaprint).

[IngwiePhoenix]

root@FriendlyWrt ~# cat .config/beets/config.yaml
plugins: duplicates convert fetchart embedart

I removed a bunch of duplicates using fdupes and also a lot of individual WAV files - memory usage has stood low, but unfortunately I was unable to find out what exactly causes the issue.

I am left assuming that the amount of files was at least part of the problem...