Reply To: performance differences between itunes and nslu2


Hmmm right…

* another table (ouch *g*), simple songid-playlistid.
* updating this table (add & remove) whenever a smart playlist is changed.
* updating this table (add) when the scan finds new songs.

Hmmm sorry… thinking too much in databases recently… just have a separate file named playlist.cache in the cache folder and put each song id as an unsigned long in there and thats it, even with 20k songs, that would not mean too much in memory while using it as a help in processing.