apologies for the following comparison with Plex, i hope a comparison is reasonable/helpful in this instance.....
Whilst investigating an issue the other day i had cause to look at the raw emby and Plex databases.
I noticed that the Plex has 1 database with different tables for different datatypes, and precooked indexes to speed up common select statements, with an app memory footprint 1/20th-1/50th of emby and a speed of anywhere between same to 50 times slower on the same hardware...for similar user functions eg. show album artists..
I noticed emby has a few separate database, and uses blobs to store text attributes for media parts....with less separation of data types into table types...and no? person/artist database
Is album artist performance slow for large collections because their is no table dedicated to people/artists which can be queried immediately and indexed?
The design decision of emby to support multiple album artists, album as well as artist bios, rich image metadata, gives emby the potential of being best for music, but currently the performance is seriously hampering the product (imo for use with larger collections).
Could the devs share their thoughts on DB design/album artist performance?..this is what i am selfishly interested in...perhaps there are others too...please speak up/lend weight to discussion.