From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 24 00:17:11 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 5C30F106566C; Fri, 24 Feb 2012 00:17:11 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-197-151.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id E6E9C1577E1; Fri, 24 Feb 2012 00:17:10 +0000 (UTC) Message-ID: <4F46D706.1060903@FreeBSD.org> Date: Thu, 23 Feb 2012 16:17:10 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20120218 Thunderbird/10.0.2 MIME-Version: 1.0 To: John Baldwin References: <4F45AB76.5050201@FreeBSD.org> <201202230822.16304.jhb@freebsd.org> In-Reply-To: <201202230822.16304.jhb@freebsd.org> X-Enigmail-Version: 1.3.5 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, "hackers@freebsd.org" , Ivan Voras Subject: Re: PostgreSQL benchmarks (now with Linux numbers) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2012 00:17:11 -0000 On 02/23/2012 05:22, John Baldwin wrote: > On Wednesday, February 22, 2012 9:59:02 pm Doug Barton wrote: >> On 02/22/2012 01:42, Ivan Voras wrote: >>> The Dragonfly team has recently liberated their VM from the giant lock and there are some interesting benchmarks comparing it to FreeBSD 9 and a > derivative of RedHat Enterprise Linux: >>> >>> http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00008.html >>> >>> Other developments are described in their release notes: http://www.dragonflybsd.org/release30/ >> >> The 4.5 times improvement by enabling kern.ipc.shm_use_phys is pretty >> notable, what prevents us from enabling that by default? > > It makes all your SYSV SHMs wired. That's fine if you are running a dedicated > server using SYSV SHMs where you want that process to use all the RAM in the > machine (e.g. a pgqsl server). It's not so great for a general purpose load > where you would like an otherwise-idle process using SYSV SHMs to have the SHMs > paged out to swap if other processes on the machine need memory and the box is > under memory pressure. I see, thanks for that explanation. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/