A Question Of RAM...
A Question Of RAM...
Wasn't sure whether this could really be classed as a bug and wanted to get some feedback/confirmation from other users.
From a clean boot on my system Live 4 uses approx 40Mb's worth of RAM - Live 5.0.1 uses over 200Mb and that's just to get the app up and running never mind clips etc. Purely as a matter of interest what's being loaded up in 5 that wasn't in 4? Is the Live Packs or something else? Sure I understand that any update to software is generally combined with an increase in specs - but 5 times the amount of memory for the application seems a bit steep?
From a clean boot on my system Live 4 uses approx 40Mb's worth of RAM - Live 5.0.1 uses over 200Mb and that's just to get the app up and running never mind clips etc. Purely as a matter of interest what's being loaded up in 5 that wasn't in 4? Is the Live Packs or something else? Sure I understand that any update to software is generally combined with an increase in specs - but 5 times the amount of memory for the application seems a bit steep?
Strange...
My Live 5 uses 37 meg right now, with plugs and clips.
That's *just* 10 megs more then FireFox is taking.
(PC)
// C
My Live 5 uses 37 meg right now, with plugs and clips.
That's *just* 10 megs more then FireFox is taking.
(PC)
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
Hi Conny - appreciate your, and others, feedback on this. How are you measuring your RAM usage? I'm using CachemanXP on a seriously tweaked install of WinXP SP1a - there's only 7 services running in the background. As I said above loading Live 4 gives similar results to what you've stated above - approx 40Mb - but in Live 5.01 the usage goes up massively.conny wrote:Strange...
My Live 5 uses 37 meg right now, with plugs and clips.
That's *just* 10 megs more then FireFox is taking.
(PC)
// C
I just check the memory usage in task manager, don't know if that is the OK way.
// C
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
Oops, right now when first checking a clean set, it was up at 67 megs.
Another set with NI Vokator in Live 5 goes up to 116 megs.
Don't have Live 4 on this machine to compare.
//
Another set with NI Vokator in Live 5 goes up to 116 megs.
Don't have Live 4 on this machine to compare.
//
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
This is crazy.
Had task manger opened, doing other things, then Live was down to 6 megs for some time then suddently was up at 87 megs. And I did not even use Live, it was just opened.
// C
Had task manger opened, doing other things, then Live was down to 6 megs for some time then suddently was up at 87 megs. And I did not even use Live, it was just opened.
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
And now it's 96 meg, empty set, still not used for anything.
// C
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
-
- Posts: 5788
- Joined: Wed Nov 24, 2004 11:05 pm
- Location: Melbourne Australia
- Contact:
Opened a set with lots of samples: 240 meg.
Opened a clean set after that: 138 meg!!!
Seems memory is not returned/cleared correctly.
Check this out:
Open Live fresh.
Check mem usage while creating new default sets.
For every new set, memory usage rises with aprox 0.5 to 1 meg...
// C
Opened a clean set after that: 138 meg!!!
Seems memory is not returned/cleared correctly.
Check this out:
Open Live fresh.
Check mem usage while creating new default sets.
For every new set, memory usage rises with aprox 0.5 to 1 meg...
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
VM is like twice the mem usage for Live 5 here.
New set, VM 154 meg.
Compared with Melodyne: 13 meg.
// C
New set, VM 154 meg.
Compared with Melodyne: 13 meg.
// C
PC Laptop Acer, XP Home SP2, build in crappy sound card.
Bleeps and Blops!
http://bluemoose.greatnow.com/
Bleeps and Blops!
http://bluemoose.greatnow.com/
Cheers again for the feedback guys. I don't know whether this is just something on my system but I don't think I'm that much of a noob as far as setting up a DAW goes My sys is a P4 2.6c, D865PERL board, 512 Mb PC3200, Audiophile 24/96 - clean install of XP tweaked like mad as per the Blackviper site.
From a cold boot into a clean set I get the following results:
Live 4.1
Windows Task Manager
Mem Usage : 40Mb
Commit Charge : 98Mb increasing to 150Mb
PF Usage : 150 Mb
CachemanXP
Physical Memory Usage : 121 Mb increasing to 160Mb
Paging File Usage : 7.9Mb increasing to 37.4Mb
Live 5.01
Windows Task Manager
Mem Usage : 206Mb
Commit Charge: 98 Mb increasing to 338Mb
PF Usage : 338Mb
CachemanXP
Physical Memory Usage : 121Mb increasing to 338Mb
Paging File : 7.9Mb increasing to 21.3Mb
Does anyone have any idea what's going on? Yeah I know I should really slap in another 512Mb of RAM but why is V5 using 5 times as much RAM when it isn't even doing anything?
From a cold boot into a clean set I get the following results:
Live 4.1
Windows Task Manager
Mem Usage : 40Mb
Commit Charge : 98Mb increasing to 150Mb
PF Usage : 150 Mb
CachemanXP
Physical Memory Usage : 121 Mb increasing to 160Mb
Paging File Usage : 7.9Mb increasing to 37.4Mb
Live 5.01
Windows Task Manager
Mem Usage : 206Mb
Commit Charge: 98 Mb increasing to 338Mb
PF Usage : 338Mb
CachemanXP
Physical Memory Usage : 121Mb increasing to 338Mb
Paging File : 7.9Mb increasing to 21.3Mb
Does anyone have any idea what's going on? Yeah I know I should really slap in another 512Mb of RAM but why is V5 using 5 times as much RAM when it isn't even doing anything?
OSX 10.4.2
Using Activity Monitor to measure Real Memory and Virtual Memory Usage.
Blank and Identical Empty Template .als
Live 5 - 45MB Real RAM, 283MB Virtual RAM
Live 4 - 42MB Real RAM, 217MB Virtual RAM
_________________________________________
Live Set made in Live 4 of 7 Audio Clips, 1 Midi Channel.
a few EQ4's, a few CompII's, AUMatrixReverb, EAS Finis, Filterscape VA, a couple Hydratones, PSP MixSaturator.
During Playback:
Live 5 - 148MB Real RAM, 408MB Virtual RAM
Live 4 - 149MB Real RAM, 344MB Virtual RAM
Close and ReOpen .als (without quitting Live.app(s) ) During Playback:
Live 5 - 148MB Real RAM, 408MB Virtual RAM (same as above)
Live 4 - 188MB Real RAM, 512MB Virtual RAM (much higher than before)
Delay comp in Live 5 turned off, and every preference in Live 4 set to be the same in Live 5.
wierd results, especially with the ReOpen in Live 4.
Using Activity Monitor to measure Real Memory and Virtual Memory Usage.
Blank and Identical Empty Template .als
Live 5 - 45MB Real RAM, 283MB Virtual RAM
Live 4 - 42MB Real RAM, 217MB Virtual RAM
_________________________________________
Live Set made in Live 4 of 7 Audio Clips, 1 Midi Channel.
a few EQ4's, a few CompII's, AUMatrixReverb, EAS Finis, Filterscape VA, a couple Hydratones, PSP MixSaturator.
During Playback:
Live 5 - 148MB Real RAM, 408MB Virtual RAM
Live 4 - 149MB Real RAM, 344MB Virtual RAM
Close and ReOpen .als (without quitting Live.app(s) ) During Playback:
Live 5 - 148MB Real RAM, 408MB Virtual RAM (same as above)
Live 4 - 188MB Real RAM, 512MB Virtual RAM (much higher than before)
Delay comp in Live 5 turned off, and every preference in Live 4 set to be the same in Live 5.
wierd results, especially with the ReOpen in Live 4.
*bump*
started related thread:
http://www.ableton.com/forum/viewtopic. ... highlight=
ableton has to know there is a serious problem with this ...
.
started related thread:
http://www.ableton.com/forum/viewtopic. ... highlight=
ableton has to know there is a serious problem with this ...
.
--
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com