Feature requst: test case for large database

Discuss client development (or even MPD development if you feel so inclined), ask questions about the client libs, MPD feature requests from client developers, etc...
Post Reply
skidoo
Posts: 208
Joined: April 28th, 2013, 10:06 pm
Location: Western Germany

Feature requst: test case for large database

Post 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?

max
Forum team
Posts: 1130
Joined: January 15th, 2013, 3:43 pm

Re: Feature requst: test case for large database

Post 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.

skidoo
Posts: 208
Joined: April 28th, 2013, 10:06 pm
Location: Western Germany

Re: Feature requst: test case for large database

Post 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.

geneticdrift
Posts: 3
Joined: September 9th, 2013, 8:49 am

Re: Feature requst: test case for large database

Post by geneticdrift »

skidoo wrote:
February 12th, 2020, 10:46 pm
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

Post Reply