On Wed, 2005-07-06 at 20:14 -0400, Colin Walters wrote: > > Now an implementation detail one could be concerned about now is that > Rhythmbox takes up a lot of memory when it's running. I bet this (along > with getting the library saved) are the reasons people actually want to > quit Rhythmbox. But both of those are just *bugs* in this model. > There's no reason I can think of for example that we couldn't instead of > the XML crack do an mmap database which Rhythmbox could use directly. > When the window is closed and nothing is playing back, we simply unmap > the database. Memory usage problem solved. The library saving thing is > obviously a plain old bug. I've been playing around to a couple of memory tools (particularly the valgrind tool massif) and have fixed a couple of fairly big leaks, and other memory usage bits in RhythmDb. I'm looking at dealing with some of the memory fragmentation issues at the moment. With those patches applied (they might not have gotten out to anonymous cvs yet) you save fair bit of RB's non-gstreamer memory. For me (with a ~3500 song library) GStreamer buffers now take up around 40-50% of the heap. Cheers, James "Doc" Livingston -- Never meddle in the affairs of cats, for they are subtle and will pee on your computer.
Attachment:
signature.asc
Description: This is a digitally signed message part