mt-daapd 0.2.4 question and issues

[jiceher]

Hi,

I used mt-daapd 0.2.4 since several month and I notice some trouble:

1) I want to use the stable version of the server only because the fact I don’t want to update often my system;

2) We can’t use multiple content directories. I hace already make my own patch to enable this feature and it seems to work well. This is not a issue but just a remark;

3) We can launch mt-daapd without mdnsd support (option -m) but what is for ? With this option mt-daapd database is no more viewed in different itunes client on the network;

4) I have memory trouble with gdb, I have 10000 songs, it corresponds to a 7Mo songs.gdb file and when someone is connect to the server, it takes more than 22Mo on memory. Doest it a normal memory usage ? I plan to use mt-daapd with small embedded system (like via mini-itx motherboard) with small amount of memory (128Mo for the whole system) and I found the memory usage of the server not appropriate. More, I have notice that the memory doesn’t free when the client is disconnected.

Thanks,

JiCeheR

[rpedde]

@jiceher wrote:

1) I want to use the stable version of the server only because the fact I don’t want to update often my system;

svn-1359 is pretty stable.

3) We can launch mt-daapd without mdnsd support (option -m) but what is for ? With this option mt-daapd database is no more viewed in different itunes client on the network;

In case you want to use static entries in your mdns responder. Or if there is no need because you are running it over a tunnel and have to run a proxy mdns responder anyway.

4) I have memory trouble with gdb, I have 10000 songs, it corresponds to a 7Mo songs.gdb file and when someone is connect to the server, it takes more than 22Mo on memory. Doest it a normal memory usage ? I plan to use mt-daapd with small embedded system (like via mini-itx motherboard) with small amount of memory (128Mo for the whole system) and I found the memory usage of the server not appropriate. More, I have notice that the memory doesn’t free when the client is disconnected.

That’s probably the effect of heap fragmentation. 0.2.4 builds the dmap tree in memory before streaming it. Makes it unuseable on small machines like a NSLU2 with over 8K or so songs. Nightlies trade two passes on the database for memory, and consequently can serve more songs on smaller machines, although it does pay a performance penalty.

Bottom line, if you are running an embedded machine with a large database, you are better off with nightlies.

— Ron

[jiceher]

I have just compiled and tests nightlies 1359 and it works fine.
I use sqlite2 and I confirme that it takes less memory and cpu usage than gdbm.
For exemple with a 30000 songs files catalog it used 4.5Mo of memory in place of 23.
The disk size of the database is bigger but we dont care.

Thanks a lot for your reply

[Author]

Posts