From: Roland Titze on
On 28 Mai, 09:18, kielhd <kie...(a)freenet.de> wrote:
> HI NG,
>
> I need to find out how nuch RAM is still available on the system. Is
> there a command that gives me ONLY the availably RAM (not including
> swap-space!) ?
>
> TIA,
> Henning

Hi Henning,

the command

echo "::memstat" | mdb -k

gives some information how the physical memory
is used. Unfortunately this command is very slow
and only usable as user root.

BR
--
Roland
From: Richard B. Gilbert on
Ian Collins wrote:
> On 05/28/10 07:18 PM, kielhd wrote:
>> HI NG,
>>
>> I need to find out how nuch RAM is still available on the system. Is
>> there a command that gives me ONLY the availably RAM (not including
>> swap-space!) ?
>
> How do you define "available RAM"?
>

Lacking any further info I'd have to assume he's asking how much RAM is
installed.

The OP might find this to be of some interest:

http://catb.org/~esr/faqs/smart-questions.html

A well posed question is more likely to get a useful answer than one to
which no thought has been given.
From: Michael Laajanen on
Hi,

kielhd wrote:
>> - prtconf display the physically installed memory
>
> Thank you for your answer, but I am actually looking for RAM, that is
> available for processing, not for the installed RAM.
> sysstat [1] is not available on the system, unfortunately.
>
> Is there another way to get this information?
>
> TIA,
> Henning
I think that that is not easy to find out since not all memory is
returned until it is needed thats the whole point of having a efficient
memory system, not wast CPU cycles until there is a need for it.

Is it not enough to know total amount of memory and then use start the
app or not.

Using other counters like sr(in vmstat 1) will once started tell you if
you are in any need of more physical RAM or not.


/michael
From: Andrew Gabriel on
In article <17753f80-d78b-4fa7-8664-9ad51ee33bc2(a)o1g2000vbe.googlegroups.com>,
kielhd <kielhd(a)freenet.de> writes:
>
>> - prtconf display the physically installed memory
>
> Thank you for your answer, but I am actually looking for RAM, that is
> available for processing, not for the installed RAM.
> sysstat [1] is not available on the system, unfortunately.
>
> Is there another way to get this information?

The question is too imprecise to provide any answer.
However, I suspect that even if you asked a more precise
question, it's still not going to have a simple answer;
you really need to go and read up on how system memory
allocation works. Thinking that the system keeps memory
free for you to use is misleading. A better way to think
of it (but still too simplistic) is that the system will
find you some memory when you need it, by taking it from
other things that need it less than you do. After all,
why keep it free - that's just wasting the memory you
purchased. As you need more memory, the system will take
it from increasingly important other things, and this
will eventually start to impact their performance
noticably, and eventually the performance of your
application and the whole system. It's a sliding scale,
and you might not hit any hard limit until the system
is performing too poorly to be effective. There are
copious resource controls available in Solaris which you
can use to impose limits if you need to protect aspects
of system performance from such degradation.

--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]
From: Canuck57 on
On 28/05/2010 2:26 AM, kielhd wrote:
>
>> - prtconf display the physically installed memory
>
> Thank you for your answer, but I am actually looking for RAM, that is
> available for processing, not for the installed RAM.
> sysstat [1] is not available on the system, unfortunately.
>
> Is there another way to get this information?
>
> TIA,
> Henning

Why would you need another way? Isn't going to change the results.

--
I would rather be a paid up Conservative nut job than a Liberal with no
nuts, no job in debt and living off of other people like a leach.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: disk space usage
Next: Suggession for your website