Page 1 of 1

Feature requst: test case for large database

Posted: February 12th, 2020, 10:46 pm
by 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?

Re: Feature requst: test case for large database

Posted: February 13th, 2020, 8:08 am
by 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.

Re: Feature requst: test case for large database

Posted: February 13th, 2020, 3:25 pm
by 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.