OSX- Activity Monitor Confusion

[JWL]

Hey folks:

I'm looking for a detailed explanation of how Virtual Memory works when loaded apps (including VI Cube).

With 8GB of RAM installed and 9 GB assigned to Virtual Memory, I see that I have (for one particular project) 4.5 GB wired and 3.5 GB free...

Yet, I'm getting an error message that I'm out of resources.

[*-)]: [*-)]: [*-)]: [*-)]:

And, no, there's nothing wrong with the RAM-- just had everything checked out. Activity Monitor sees all 8GB-- but I can't sort out what *resources* I've run out of.

There are no effects or other plugins loaded.

This isn't a drive bus issue-- because everything is at a standstill.

This isn't a CPU issue, because it's reading less than 50% at a standstill.

On the surface, it's not a RAM resources issue-- with almost HALF the installed RAM marked as being "free".

G5 2.5 Dual PPC, OS 10.4.8

I just want to know where I can find a detailed explanation of how data is threaded into Virtual Memory-- and what happens with VI instances and samples when less than 3GB of samples are loaded (the rest being used by Digital Performer, OSX and other services... and with 3.5 GB RAM free.

I do understand all too well about the 3-4GB limit of 32-bit apps and that data above and beyond that will be threaded into that limitation as needed.

I just have no idea what "resources" I've run out of.... [:'(]

Help? Anyone?

[Jerome]

Where do you get that message?

[JWL]

@Jerome said:

Where do you get that message?

While loading instances in DP during the process of samples from a template loading. I forced-quit the DAW and started again with Activity Monity open just to watch the numbers.

I've since deleted some of the instances and have reduced my template as a matter of commone sense with a measure of success-- ie: no error message.

I'm still baffled by the amount of available RAM and the comparatively low CPU meter reading to have expended my resources so easily.

... and it seems rather unpredictable. In another template I've had 11GB allocated to VM with no error messages-- with only 500 MB of available RAM.

[plowman]

"On the surface, it's not a RAM resources issue-- with almost HALF the installed RAM marked as being 'free.' "

I'll get "out of memory" prompts in Logic. Activity Monitor may be reporting over 2 GB free, but I get the prompts because Logic itself is tapped out at the program max of 3.5 GB. Where are you getting the prompt -- within which program? Is anything on the Activity Monitor list near the 3.5 GB capacity?

[JWL]

@Plowman said:

"On the surface, it's not a RAM resources issue-- with almost HALF the installed RAM marked as being 'free.' "

I'll get "out of memory" prompts in Logic. Activity Monitor may be reporting over 2 GB free, but I get the prompts because Logic itself is tapped out at the program max of 3.5 GB. Where are you getting the prompt -- within which program? Is anything on the Activity Monitor list near the 3.5 GB capacity?

Plowman-- I'm sure you're right-- it makes tons of sense.

Except one of my projects loaded up just fine-- that 11G project-- no warnings.

To answer your Q:

I'm using Digital Performer, and since I've already pointed to just over half the RAM as a benchmark, this supports your theory.

Activity Monitor is not showing any one thing in the 3.5GB range-- just a total of 4.5GB wired.

I suppose my question shifts to the reasons why the 11G project works fine and the 5G project conks out.

[cm]

JWL, i think first we have to check how your 11G project is in detail, because samples cannot use virtual memory - loading 11GB on a machine with 8GB RAM doesn't work. (simplified: virtual memory is code or data outsourced to a pagefile on your harddisk, so streaming from harddisk to a file on a harddisk doesn't make any sense)

if your sequencer *calls* different applications, each running in it's own memory space, you can break the 3,5 GB limit for a single application. the first application hitting the 3,5 GB barrier (for it's own memory space) stops the whole setup to work.
christian

[JWL]

@Another User said:

if your sequencer *calls* different applications, each running in it's own memory space, you can break the 3,5 GB limit for a single application. the first application hitting the 3,5 GB barrier (for it's own memory space) stops the whole setup to work.
christian

Hence-- this is where standalone is indespensable. I've gotten a remarkable amount accomplished without using standalone instances-- and why one or two bigger projects slotted themselves in so neatly will ever remain a mystery. But, if I've learned nothing else, I've learned not to expect things to always work that way or to ever expect for them to work any other way than the way you've described.

Even if I could get a good string section running inside my DAW and a good sized wind section running outside of it, I'm lightyears ahead. Mixing would be ever so much simpler, and putting in brass and percussion after the fact would require less guesswork.

It's very important for me to understand how to get the most out of any one machine. I've been talked out of considering the Muse Receptor as a VI host-- so, its 2GB of RAM falls short of the proverbial 3.5 GB brick wall, but for the price and the uncertainties with the Receptor it seems that an Intel will be the best addition to my G5. There may also be a Mac Mini petting zoo to add to the farm as well.

Sorry guys-- I'm not pulling down $100k a week which would facilitate having a complex 9 computer setup. It really has taken me 2-3 years to get to this point. Ironically, the money spent on the software would have paid for the hardware quite handsomely! I simply had to make a choice and then work in small steps. Please forgive me if my posts are overly basic and a little behind the curve.

Thanks all the same,
JWL