From: | Curt Sampson <cjs(at)cynic(dot)net> |
---|---|
To: | Gregor Mosheh <stigmata(at)blackangel(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: memory strangeness (fwd) |
Date: | 2002-07-07 04:06:00 |
Message-ID: | Pine.NEB.4.44.0207071301240.487-100000@angelic.cynic.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, 5 Jul 2002, Gregor Mosheh wrote:
> I'm aware of the problems of over-allocating RAM, and I surely wouldn't
> want to force the buffers into swap. (thanks, Curt, for
> kern.ipc.shm_use_phys) On this particular system, though, it's doing
> nothing except PG. 384 MB of RAM, I can give PG 160 of it, which leaves me
> with some 170 MB of idle RAM.
No, that's not idle RAM; that's buffer cache. (FreeBSD, like most
modern Unix operating systems, will use any spare physical memory
to cache blocks read from the disk.) If you allocate 160/170, you
now have pretty much maximized your chances that postgres and the
operating system will be buffering the same data, and made your
memory as minimally effective as possible.
> I'd read somewhere (obiously outdated) that the MAXDSIZ was 128 MB. I've
> since rebooted with the kernel.GENERIC... What's the sysctl setting I use
> to set/check the data size limits?
It's not a sysctl, because those limits are settable per-process.
Use "ulimit -aS" to check the current (soft) limits, and "ulimit
-aH" to check the hard limits (beyond which the soft limits may
not be raised). Also see the getrlimit manpage.
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah. | 2002-07-07 13:29:01 | Re: Which DB is using space. |
Previous Message | Tom Lane | 2002-07-06 14:57:19 | Re: WAL files in 7.2 vs. 7.1 |