Michael Herger wrote:
Adding 1500 files takes 50 seconds. This is very very slow, and I'm
totally convinced this could be speeded up by at least an order of
magnitude by simple optimization in the way slimserver handles the
database. Basically, the SQL engine should be allowed to do more of the
work.
Adding/scanning files is much more than just inserting a few records:
folders are scanned (disk i/o), file types are checked, tags verfied
and/or guessed etc. I doubt MySQL could do that.
No, it couldn't. But surely this kind of operation should only be done
while adding diskfiles to the track database? Not while adding (already
indexed) tracks to a playlist? Or is that the real problem here? If I
want to 'play' my 'Classical' folder tree, does slimserver do a full
rescan for that tree? I don't think it should be doing that, because it
makes creating a playlist very slow if you use the 'Music Folder' way of
browsing. I understand from this forum that I'm not the only one who
uses slimserver this way.
Regards,
Peter
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
