A playlist is basically just a directory listing, right? I can't imagine it would take too long. Other media servers often
index files into a database of some kind, which is a very different process and takes time.
The amount of time to generate a playlist depends largely on your filesystem. On my ext4 drive:
- Code: Select all
user@host:~$ time find ./ -name *.avi | wc -l
114
real 0m6.658s
...and after that's been done once:
- Code: Select all
user@host:~$ time find ./ -name *.avi | ls -l > /dev/null
real 0m0.389s
When I did this to find over 34k music files (FLAC, OGG, and MP3 all at once) on my media drive (also ext4), it took maybe 15 seconds to do the initial find. Then to cat the directory listings to a file took less than a third of a second. (Sorry, didn't think to time that one, and now all my subsequent finds are about 0.3 seconds.)
On NTFS or FATx, you might be looking at longer loading times. It also, of course, has a lot to do with the speed of your drive. Sorry, don't have an NTFS drive handy to test at the moment.
Can anyone run a similar test on a Windows machine (with any FS)? I have a feeling that makes a difference as well. I'll check my OGG dir on my Win7/NTFS machine later if I remember.
I don't think this would be a very time consuming process. And it would only have to be done when changes are made to the library (or upon request, I suppose). Unless your running on a Pentium II or reading your library from magnetic tape, I doubt it would be unbearably slow.
EDIT: Put terminal output in code tags.