Hey, this is really cool. I directly tried the script and there's a line
from the output that caught my eye:
> mem_gap_vm: + 8812892160 ( 8404MB) [ 26%] Memory gap: UNKNOWN
is this the shared buffers? I guess so, but I want to confirm my guess ...
Frank
Am 2012-11-07 09:26, schrieb Achilleas Mantzios:
> Vick,
> fantastic script, thanx! FreeBSD sysctl system is awesome!
>
> On Τρι 06 Νοε 2012 14:33:43 Vick Khera wrote:
>
>
>
> On Mon, Nov 5, 2012 at 10:11 AM, Frank Broniewski <brfr@metrico.lu> wrote:
>
> and this is after a few hours of running:
>
> Mem: 91M Active, 17G Inact, 3983M Wired, 1526M Cache, 3283M Buf, 155M Free
> Swap: 4096M Total, 828K Used, 4095M Free
>
>
>
>
> For comparison, here is the output of a 32GB FreeBSD 9.0/amd64 server, with Postgres 9.0.7 running since June 10, and
isheavily pounded on 24x7. The data + indexes are about 240GB on disk. This server only runs postgres aside from the
basicsystem processes.
>
>
> Mem: 231M Active, 21G Inact, 3777M Wired, 1009M Cache, 3285M Buf, 191M Free
> Swap: 4096M Total, 272K Used, 4096M Free
>
>
> I agree with the conclusion that the shared memory segments are confusing the output of top. There are no memory
leaks,and FreeBSD doesn't "lose" any memory.
>
>
> There are some scripts floating around that read values from sysctl vm.stats.vm and format them nicely to tell you
howmuch memory is used up and free. Try the one referenced here:
http://www.cyberciti.biz/faq/freebsd-command-to-get-ram-information/
>
>
>
>
>
> -
> Achilleas Mantzios
> IT DEPT
>
--
Frank BRONIEWSKI
METRICO s.à r.l.
géomètres
technologies d'information géographique
rue des Romains 36
L-5433 NIEDERDONVEN
tél.: +352 26 74 94 - 28
fax.: +352 26 74 94 99
http://www.metrico.lu
