As promised, I look next into the memory usage of each of the players in this biannual music player review. Note, these tests are on a 64 bit machine, so they would be about double compared to a 32 bit machine.
I wanted to reduce the affect of shared libraries on these results. So I started each program individually via the startx command. No other program should have been running. The one exception is amarok, who couldn’t start that way (it crashed).
After reviewing about 3 different ways to measure memory I gave up and went pack to ps. The two memory numbers I measured were VSZ (virtual) and RSS (resident memory). Or in other words:
- virtual memory – memory app has requested and can address
- resident memory – memory currently in use ~ much better measure of actual memory usage
It’s important to note that there are many articles describing how you can’t measure memory usage perfectly on Linux. I provide the virtual memory for reference, but the RSS is what I would consider the key metric. Don’t consider the results “absolute”, but it should be good enough to get some trends from.
These ratings are only based on RSS:
Best: Audacious, followed closely by Musique.
Second Best: Guayadeque & Banshee. Banshee was the worst in my previous review, where I was very concerned about it using 40 MiB of memory (on 32 bit). I even complained that not all of us have 4 GB of ram (I now do.. oops) when it was chosen to replace Rhythmbox in the default Ubuntu cds. Although Banshee did end up getting removed for political reasons (mono related), kudos to them for improvement in the memory usage space.
Average: At about 100 MiB on a 64 bit machine. Clementine and Gmusicbrowser were slightly better than Quod Libet and Rhythmbox.
Worst: In a category of it’s own is Amarok, The first time I tested Amarok, it used 700 MiB. It’s *only* at 400 MiB in “real” memory usage now though. It also had a weird virtual memory jump.
Tune in next time for CPU usage when playing a song.