Feature requst: test case for large database

[skidoo]

Some MPD clients seem to have problems with large (here > 180k songs) MPD (from git, on Debian x64 testing) databases. Android clients take ages at startup or Windows clients hang on database update. How about a test case which simulates a large database to help developers to optimize clients?

[max]

Some MPD clients insist on downloading the whole MPD database when they connect, and some even maintain a shadow copy of the database. These clients are inherently broken, and I will do nothing to support this broken behavior.

There's nothing clients can "optimize" at this - clients must not download the whole database, and should instead only request the portion they're currently interested in.

[skidoo]

Some MPD clients insist on downloading the whole MPD database when they connect, and some even maintain a shadow copy of the database. These clients are inherently broken

Yes. Adding a test case makes nasty client behaviour obvious to users.

[geneticdrift]

How about a test case which simulates a large database to help developers to optimize clients?

This may be what you are looking for: Generating large music collection for testing