Shanty/Main
1
0
Fork 0
Code Issues 9 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Updated docs
CI / check (push) Successful in 1m10s
Details
CI / docker (push) Successful in 1m35s
Details

Browse Source
This commit is contained in:
Connor Johnstone
2026-03-23 16:52:01 -04:00
parent 53b3a644a1
commit 6821427471
8 changed files with 65 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/musicbrainz-db.md
+1 -1
View File
@@ -20,7 +20,7 @@ If you are casually using Shanty for a few artists, the caching system works wel
- **Download size:** approximately 24 GB (compressed JSON dumps from MusicBrainz)
- **Database size:** approximately 16 GB (the resulting SQLite database)
- **Disk type:** SSD strongly recommended. The import writes millions of rows, which is very slow on spinning disks.
- **Disk type:** SSD strongly recommended for best performance. On an SSD, artist pages load in under a second. On a spinning hard drive, the database still works and is a big improvement over the API (a few seconds per page load instead of 30-60 seconds), but you will notice the difference compared to SSD.
- **Time:** 12-24 hours for the initial import, depending on your hardware and disk speed.
- **Disk space total:** You need roughly 40 GB free during import (dumps + database). After import, you can delete the dump files to reclaim the 24 GB.