fyi, there will be further optimizations before release. also, debug code will be removed so that might have a bit of an impact as well.

-Rusty

haha, i was at 400+ megs of RAM today. Currently with a restart i am using 125 megs, +/- 20 megs. depending on how many songs i am viewing. I only noticed the memory usage today because Vista told me i was low on memory. To be honest it was running very slow on switching to a new song.

Yea, my PC has been on for a little more then 10 days and well MM was most likely on the same amount. I also was on Beta 2 and just moved up to beta 3 tonight.

Possibly, I suggest that we wait till MM3 Final is out and we have clean non-debug version in hands without thousands of CODE lines, lots of internal testers, watchers, reporters, .... loaded into MediaMonkey to test speed and memory hogging.

EDIT: Regarding Memory Hog, last night I loaded Acrobat reader 8 to read one of my coding E-Books I couldn't beleive my eyes Acrobat Reader 8 with loaded E-Book took 600Mb +/- 20Mb of my RAM Repeated same proces on My mothers Computer with Acrobat reader 7 and it Took ~85Mb. E-Book is 65MB PDF

The point I was trying to make was...

While it -does- use a fair amount of RAM, especially when compared to smaller players (Such as Winamp5 in Classic Skin mode), it's right on par with iTunes and you get things like skinning which iTunes doesnt have.

I'd also like to point out that right now MediaMonkey3 Beta3 is using ~44,750k and I've had it open for a while on random play. So maybe the numbers I listed last night were a bit higher than normal.

as mentioned it is kind of a mem hog. just depends on what you are having it do.

My answer: Yes and no...

MM3B3 uses ~60,000k+/-5,000k memory while playing and my library of 2590 files loaded.

iTunes uses ~43,000k having just loaded with no songs in the library and many options unchecked (if it makes a difference).
After importing my music iTunes jumps to about 52,800k and while playing, it averages around 55,000k~56,000k. Both while playing and while not playing, I saw iTunes jump up over 63,000k somewhat frequently.


MM3 is still in Beta, so there might be a problem with the memory management or some optimizations that they haven't gotten to yet.

Theres a lot of new stuff included with MediaMonkey, and it's also a more flexible player with skinning when looked at next to iTunes.
The best comparison I can make would be to look at Winamp 2 vs Winamp 3 in terms of performance (or Classic Skin vs Modern Skin in Winamp 5). Winamp 2 out performed Winamp 3 (Classic / Modern) because of simpler skins.
Look at MediaMonkey 2's skin vs MediaMonkey 3's skin, IMO the MM3 skins are much smoother and the overall look and feel is an improvement too -- The same as Winamp 3/Modern Skin's were. But unlike Winamp 3/Modern Skin, I don't think MediaMonkey 3 suffers in the performance department.

Please, define "memory hog".

Is it just me, or is this Beta the biggest memory hog yet?