Re: swap right/play for single item?

> It's not the scanning of directories that's slow, its the grabbing of
> ID3 information from each file. 1. Cache the ID3 information for each
> song in the "current directory"  and the "current playlist".

Easy fix - should give us huge speed boost, but it doesn't solve the
problem.  Even if we didn't look at the id3 tags at all it would take a
while to scan when the playlist is created. For example I just tested on a
30GB collection with the find command:

real	0m8.155s
user	0m0.040s
sys	0m0.140s

>From a single client's perspective, 8s isn't too bad, but we can't hold
the whole server for more than a ms or so if we want to be scalable.

> 2. Fork the process (sorry Windows and Mac users) when responding to
> the web request (after any changes to the control or playlist have
> been made).  That way the speed of the connection back to the web
> client doesn't slow down the IR UI or playback.

I want to stay away from forking and threads so we can remain platform
independent.  It's not too hard to do big jobs incrementally, doing a
little bit each time we come out of select.

ID3 cache sounds like a good idea, no matter how we decide to do the
scanning.

Sean


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get your FREE VeriSign guide to security solutions for your web site: encrypting transactions, securing intranets, and more!
http://us.click.yahoo.com/UnN2wB/m5_CAA/yigFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/