I am in the throes of importing a large set of tunes for a local radio station. The music collection is approximately 550,000 tracks organized as Artist-Album-Track going back many years (that is to say, there are archeological layers of disarray in the tagging).
What I’m seeing (or think I’m seeing) is that the overall speed at which Beets imports an artist’s collection has slowed and sometimes takes a lot longer than I think it would take to do manually.
The source and destination volumes are on network volumes hosted by a dedicated local NAS box on a pretty mediocre gigabit network (sadly, but this is radio, after all). The database resides locally on a MacPro with internal SSD and a goodly amount of RAM.
I’m currently importing using a bash script that loops through a list of 100 artists as a data source per session. It executes the import and gets a new artist until it completes the list. The import is run in quiet mode (-q flag) and employs both MusicBrainz and Discogs in the process.
My question then is does anyone have an insight into what is going on behind the scenes and how to I might optimize the process in order to speed things along? As an example a list of 100 artists is taking about 3 days to complete but I think I was able to do 400 or 500 in the past in about 6-8 hours.
Thinking aloud, should I be tending to the local database and perform some kind of maintenance or indexing between sessions? The music database is currently at 168 MB.
I appreciate any feedback. Thank you for your assistance.