DM == Dror Matalon [EMAIL PROTECTED] writes:
DM which brings me back to my question why not make Freebsd use more of its
DM memory for disk caching and then tell postgres about it.
Because this is a painfully hard thing to do ;-(
It involves hacking a system header file and recompiling the
CW == Christopher Weimann [EMAIL PROTECTED] writes:
which brings me back to my question why not make Freebsd use more of its
memory for disk caching and then tell postgres about it.
CW Because you can't. It already uses ALL RAM that isn't in use for
CW something else.
No, it does not.
I noticed this passage too, but ...
Quoting from http://www.daemonnews.org/21/freebsd_vm.html :
snip*
When To Free a Page*
Since the VM system uses all available memory for disk caching, there
^
The VM system, as you can see from the article, is focused on
On Friday 27 February 2004 21:03, scott.marlowe wrote:
Linux doesn't work with a pre-assigned size for kernel cache.
It just grabs whatever's free, minus a few megs for easily launching new
programs or allocating more memory for programs, and uses that for the
cache. then, when a request
I guess the thing to do is to move this topic over to a freebsd list
where we can get more definitive answers on how disk caching is handled.
I asked here since I know that FreeBsd is often recommended,
http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html#
as a good platform for postgres,
On Thu, 26 Feb 2004, Dror Matalon wrote:
Hi,
We have postgres running on freebsd 4.9 with 2 Gigs of memory. As per
repeated advice on the mailing lists we configured effective_cache_size
= 25520 which you get by doing `sysctl -n vfs.hibufspace` / 8192
Which results in using 200Megs for
On 26 Feb 2004 at 13:58, Dror Matalon wrote:
which brings me back to my question why not make Freebsd use more of its
memory for disk caching and then tell postgres about it.
I think there is some confusion about maxbufsize and hibufspace. I looking at a
comment in the FreeBSB source
On Thu, Feb 26, 2004 at 11:55:31AM -0700, scott.marlowe wrote:
On Thu, 26 Feb 2004, Dror Matalon wrote:
Hi,
We have postgres running on freebsd 4.9 with 2 Gigs of memory. As per
repeated advice on the mailing lists we configured effective_cache_size
= 25520 which you get by doing
Thanks for the pointer. So
maxbufspace = nbuf * BKVASIZE;
Which is confirmed in
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/performance/2003-09/0045.html
and it looks like there's a patch by Sean Chittenden at
http://people.freebsd.org/~seanc/patches/patch-HEAD-kern.nbuf
that does what
On Thu, 26 Feb 2004, Dror Matalon wrote:
On Thu, Feb 26, 2004 at 11:55:31AM -0700, scott.marlowe wrote:
On Thu, 26 Feb 2004, Dror Matalon wrote:
Hi,
We have postgres running on freebsd 4.9 with 2 Gigs of memory. As per
repeated advice on the mailing lists we configured
We have postgres running on freebsd 4.9 with 2 Gigs of memory. As per
repeated advice on the mailing lists we configured effective_cache_size
= 25520 which you get by doing `sysctl -n vfs.hibufspace` / 8192
Which results in using 200Megs for disk caching.
effective_cache_size does nothing of
On Fri, Feb 27, 2004 at 05:47:47AM +0800, Christopher Kings-Lynne wrote:
We have postgres running on freebsd 4.9 with 2 Gigs of memory. As per
repeated advice on the mailing lists we configured effective_cache_size
= 25520 which you get by doing `sysctl -n vfs.hibufspace` / 8192
Which
Hi,
We have postgres running on freebsd 4.9 with 2 Gigs of memory. As per
repeated advice on the mailing lists we configured effective_cache_size
= 25520 which you get by doing `sysctl -n vfs.hibufspace` / 8192
Which results in using 200Megs for disk caching.
Is there a reason not to increase
13 matches
Mail list logo
