it would be nice to specify whether a server is capable of handling large databases

[basings]

how to make this judgable based on facts?

[BillButter]

In my head, this feels like an impossible task. We would need someone to install every entry on a machine one at a time, record a few metrics (eg. how long it takes for initial scan, how long it takes to load a 3 minute song, how quick it starts a playlist), and chart them all up.

Then this will have to be repeated every time there is a large performance update.

And it wouldn't answer questions like "Could I run this service on a pi" or "How many songs can this server reasonably handle"

That being said. I have some money. I have a domain. If someone is willing to put in the work, I will buy a VPS and point a subdomain toward it. The nice thing about this solution is that it doesn't have to be the same person to install and test each of these. And as long as we stick with the same VPS, this can easily be repeated down the line by anyone.

Optionally someone could run this from a pi. But that would require 1 person to install each, turn on one. Use their own library. Etc. Etc.