From: Jim C. Nasby <jnasby@pervasive.com>
To: Mark Kirkwood <markir@paradise.net.nz>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Kenji Morishige <kenjim@juniper.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Best OS & Configuration for Dual Xeon w/4GB &
Date: Tue, 21 Mar 2006 04:08:53 -0600
Message-ID: <20060321100852.GB15742@pervasive.com> (raw)
In-Reply-To: <441F7847.5000406@paradise.net.nz>
References: <20060317221116.GA14661@juniper.net>
<1142636433.1141.33.camel@state.g2switchworks.com>
<20060320144503.GR15742@pervasive.com>
<1142871620.17883.4.camel@state.g2switchworks.com>
<441F6BA1.20005@paradise.net.nz>
<441F7847.5000406@paradise.net.nz>
On Tue, Mar 21, 2006 at 03:51:35PM +1200, Mark Kirkwood wrote:
> Mark Kirkwood wrote:
> >
> >I think Freebsd 'Inactive' corresponds pretty closely to Linux's
> >'Inactive Dirty'|'Inactive Laundered'|'Inactive Free'.
> >
>
> Hmmm - on second thoughts I think I've got that wrong :-(, since in
> Linux all the file buffer pages appear in 'Cached' don't they...
>
> (I also notice that 'Inactive Laundered' does not seem to be mentioned
> in vanilla - read non-Redhat - 2.6 kernels)
>
> So I think its more correct to say Freebsd 'Inactive' is similar to
> Linux 'Inactive' + some|most of Linux 'Cached'.
>
> A good discussion of how the Freebsd vm works is here:
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/vm.html
>
> In particular:
>
> "FreeBSD reserves a limited amount of KVM to hold mappings from struct
> bufs, but it should be made clear that this KVM is used solely to hold
> mappings and does not limit the ability to cache data."
It's worth noting that starting in either 2.4 or 2.6, linux pretty much
adopted the FreeBSD VM system (or so I've been told).
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jnasby@pervasive.com, markir@paradise.net.nz, smarlowe@g2switchworks.com, kenjim@juniper.net
Subject: Re: Best OS & Configuration for Dual Xeon w/4GB &
In-Reply-To: <20060321100852.GB15742@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox