| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
| Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Kenji Morishige <kenjim(at)juniper(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Best OS & Configuration for Dual Xeon w/4GB & |
| Date: | 2006-03-21 03:51:35 |
| Message-ID: | 441F7847.5000406@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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."
Cheers
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Soni | 2006-03-21 05:59:54 | Perfomance test figures |
| Previous Message | Mark Kirkwood | 2006-03-21 02:57:37 | Re: Best OS & Configuration for Dual Xeon w/4GB & |