1c83f36ddf
The two album list requests reported in discussion #5929 (a 110k-album, two-library instance) were dominated by work that scaled with the whole library instead of the page: - Every native API list request also runs a count for the X-Total-Count header. album had no index covering library_id, so that count scanned the entire table on every request, dragging each row's JSON blobs through the page cache. count(distinct id) additionally built a temp b-tree over the full result set even when the query had no join that could duplicate rows. - A random sort cannot be served by an index, so SQLite evaluated SEEDEDRAND for every matching row and pushed each one, with its library and annotation joins and full column projection, through a sorter that kept only 36 rows. Add an album(id, library_id) index so library-filtered counts are served by a covering index scan, and make the shared count() helper use count(*) when the rendered query has no join, keeping count(distinct id) wherever a join could fan out rows. id leads the index deliberately: with library_id leading, the planner drives sorted list queries off it and sorts an entire library rather than walking a sort-satisfying index, and fresh statistics do not change that choice. Resolve random pages by id before hydrating them, so the sort pass runs on that covering index with no joins and only the page itself is materialized. Pages larger than 1000 keep the single-query path. The seeded shuffle is unchanged: the id query carries the caller's options, so SEEDEDRAND, explicit seeds, and the reseed-only-at-offset-0 rule all still apply, and the page is reordered in Go to preserve it. Also make the album name sort a total order by appending album.id, and widen album_order_album_name to (order_album_name, order_album_artist_name, id) to serve it. Without a tiebreaker, equal names made page order plan-dependent, which can skip or duplicate rows across paginated requests.
Navidrome Music Server 
Navidrome is an open source web-based music collection server and streamer. It gives you freedom to listen to your music collection from any browser or mobile device. It's like your personal Spotify!
Note: The master branch may be in an unstable or even broken state during development.
Please use releases instead of
the master branch in order to get a stable set of binaries.
Check out our Live Demo!
Any feedback is welcome! If you need/want a new feature, find a bug or think of any way to improve Navidrome, please file a GitHub issue or join the discussion in our Subreddit. If you want to contribute to the project in any other way (ui/backend dev, translations, themes), please join the chat in our Discord server.
Installation
See instructions on the project's website
Cloud Hosting
PikaPods has partnered with us to offer you an officially supported, cloud-hosted solution. A share of the revenue helps fund the development of Navidrome at no additional cost for you.
Features
- Handles very large music collections
- Streams virtually any audio format available
- Reads and uses all your beautifully curated metadata
- Great support for compilations (Various Artists albums) and box sets (multi-disc albums)
- Multi-user, each user has their own play counts, playlists, favourites, etc...
- Very low resource usage
- Multi-platform, runs on macOS, Linux and Windows. Docker images are also provided
- Ready to use binaries for all major platforms, including Raspberry Pi
- Automatically monitors your library for changes, importing new files and reloading new metadata
- Supports lyrics from sidecar .ttml, .yaml/.yml Lyricsfile, .elrc, .lrc, .srt, .txt files and embedded TTML, Enhanced LRC, LRC, SRT, and plain-text tags (via
lyricspriority) - Themeable, modern and responsive Web interface based on Material UI
- Compatible with all Subsonic/Madsonic/Airsonic clients
- Transcoding on the fly. Can be set per user/player. Opus encoding is supported
- Translated to various languages
Translations
Navidrome uses POEditor for translations, and we are always looking for more contributors
Documentation
All documentation can be found in the project's website: https://www.navidrome.org/docs. Here are some useful direct links:
Screenshots
