Re: API to get installed RAM
Re: API to get installed RAM
- Subject: Re: API to get installed RAM
- From: "Andy Cave" <email@hidden>
- Date: Mon, 25 Apr 2005 14:32:30 +0100
- Organization: Hamillroad Software
Hi Marc.
Simple - they would both reduce memory by a bit, rather than one by a bit
more, depending on scheduling and which one 'gets there first' etc... If you
run 2 copies of our s/w on the same machine, that's what they do. If only a
little memory less is required, one does it. If a lot less memory is
required, both tend to do it. When they reduce memory, they do it bit at a
time and continue to monitor memory, stopping as soon as possible, so don't
'blindly reduce memory'. Works well. There you go - I've given out one of
our secrets...
Andy.
----- Original Message -----
From: "Marc Epard" <email@hidden>
To: "Andy Cave" <email@hidden>; "macnetworkprog"
<email@hidden>; "Quinn" <email@hidden>
Sent: Monday, April 25, 2005 2:21 PM
Subject: Re: API to get installed RAM
on 4/25/05 8:11 AM, Andy Cave wrote:
Our application is just as clever as your OS. We monitor free phyiscal
memory and use anything 'spare' (minus a 'safety region') to cache (more)
data - makes our app fly when lots of memory is available. When the user
starts another piece of s/w, and free phyiscal memory goes down, we
reduce
our caches, which makes our application a good citizen. Just like your
OS.
How does it work when more than one app is running that uses your scheme?
-Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden