On Tue, Oct 03, 2000 at 08:57:46AM -0700, Mark B. Elrod wrote:
> 1) As I have said before make plugins load on demand rather than all at
> once on startup
Absolutely. And unload if we can, for instance the themes....
> 2) Ref count and share PlayListItems between music catalog and playlist
> manager
Moving the refcount to a higher level...interesting proposal. The
modifications might have be larger, but the benefit is more obvious.
> 3) Only create playlist items for areas of the tree that are visible or
> that are added to the playlist. For a large catalog this could make a
> real difference. It would also speed up load time. We would need to
> alter the DB though probably bc this really requires a relational DB so
> the added complexity might not be worth it.
>
This is a "keep the music catalog on disk, not in RAM" proposal. For
truly huge playlists this is a win. For small playlists, the kernel
would cache the database file and keep things speedy. By having alot
of redundancy in the database file, you might be able to avoid the
needs for a relational db. Hmm...
An intermediate step that would save memory could be this: Since gtk
widgets are copying the data, only instantiate the visible ones and
then destroy them when they are not visible in the tree. Or wait
for the MVC widgets in gtk+ version 2.
For someone with a large catalog: What is the RAM difference with no
music (remove ~/.freeamp and ~/MyMusic) and the large catalog with the
browser open and everything in the playlist?
_______________________________________________
[EMAIL PROTECTED]
http://www.freeamp.org/mailman/listinfo/freeamp-dev
