Is the bottleneck even the database in the first place? From the article, that doesn't seem to be the case: > The main case when beets writes to its database i

Is the bottleneck even the database in the first place? From the article, that doesn't seem to be the case: > The main case when beets writes to its database is on import, and import performance is dominated by I/O to the network and to music files. Small file I/O is universally slow, even on SSDs, and if you're hitting rate-limited MusicBrainz servers for each file, database performance is almost irrelevant.