Yep, 3 to 5 times would be something I would readily accept for an
interpreted language, even ten times. But 1000 times is quite a lot ;)
It's a new 400 GB standard 3,5" hard disk inside a Kurobox HG: 266 MHz,
128 MB RAM, running Debian. While I agree this is a slow NAS, it's
perfectly capable of doing the scan "fast" with mt-daapd (see numbers
below), and is able to serve half a dozen clients (haven't tested more)
- so with its 7W of power consumption it was the best choice for me :)
Currently 18895 songs, all having both ID3v1 and ID3v2 tags, most
having small album art pictures embedded (10-30kb, following ID3v2
standard, nothing special). Imho there are no broken tags (I ripped
everything myself from my own CDs, and later upgraded tags with my own
software to make sure the tags are 100% following the standard and
exactly the way I like them - also, mt-daapd would complain about
those).
I checked my mt-daapd log and this was the longest time I found (full
database rescan, I admit it's 14, not 10, minutes :D ):
Code:
--------------------
2006-10-03 19:19:31 (00004000): Scanned 17910 songs (was 17910) in 848
seconds
--------------------
A simple scan for changes takes about 100 seconds.
I can't say exact details for SlimServer, since /var/log/slimserver
exists, but was empty for as long as I can remember (is there any way
to have this filled?). I remember the last time I just rescanned the
SlimServer database; I started this one Saturday morning and was
wondering on Saturday noon that it was still scanning.
The box is running nothing but mt-daapd and slimserver, with mt-daapd
not having been used during the rescan.
--
Blubbels
------------------------------------------------------------------------
Blubbels's Profile: http://forums.slimdevices.com/member.php?userid=6728
View this thread: http://forums.slimdevices.com/showthread.php?t=18586
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/unix
