Issues with import speed despite no visible bottlenecks

[mncho]

Hello, this one has pretty damn good server hardware, but it's noticed after a certain amount of songs (10k~ of a 15k~ library or so in the beets db, know this because this one re-imported it several times thinking maybe ti was some corruption) the import speeds become absolutely abysmal. It doesn't even appear to be due to running out of resources either, as beets is really barely using memory, disk, CPU, etc. In fact, it seems to not be doing anything for long periods of time. This one can finish the prompting, and yet it still (as one example for the last import which this one did) took over 5 hours for less than 20 albums!

This one noticed that at a certain point it seemed that it stopped moving files, as it would import albums but then, in this ones file explorer it would just see them sit there full and not being moved or modified for ages even as the importer kept prompting for new albums. Eventually, this one saw one album got moved and written (finally)... But then it seemed to just sit there doing absolutely nothing again.

This one ran with the '-v' option, and it saw the truth of what was happening, for no reason it seems to just be sitting there doing literally nothing for upwards of 10 minutes between each album, and then it imports just one really quickly.... And then goes back to sitting there doing nothing until it starts to import the next one (finally).

Is there something this one is missing here or a way to run the importer faster? It really loves the convenience of beets but if it is this slow with such low number of songs, even Picard or manually tagging is actually preferable to this speed. Thank you for your time.

[mncho]

coverartarchive.org is not responding, so it's actually just been hanging waiting for it to give it art for like 20 minutes at a time and that was what was slowing it down... This one didn't even know it WAS getting coverart but its enabled by default on the docker release apparently. It had literally no indication this was what was happening, apologies