From owner-freebsd-performance@FreeBSD.ORG Tue Aug 12 19:37:14 2014 Return-Path: Delivered-To: performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30344A8; Tue, 12 Aug 2014 19:37:14 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07FE125D0; Tue, 12 Aug 2014 19:37:14 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id EB40BB949; Tue, 12 Aug 2014 15:37:12 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: PostgreSQL performance on FreeBSD Date: Tue, 12 Aug 2014 14:09:40 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <20140627125613.GT93733@kib.kiev.ua> <20140716132938.GB93733@kib.kiev.ua> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201408121409.40653.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 12 Aug 2014 15:37:13 -0400 (EDT) X-Mailman-Approved-At: Tue, 12 Aug 2014 19:38:04 +0000 Cc: Konstantin Belousov , Adrian Chadd , performance@freebsd.org, "current@freebsd.org" X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 19:37:14 -0000 On Wednesday, July 16, 2014 1:52:45 pm Adrian Chadd wrote: > Hi! > > > On 16 July 2014 06:29, Konstantin Belousov wrote: > > On Fri, Jun 27, 2014 at 03:56:13PM +0300, Konstantin Belousov wrote: > >> Hi, > >> I did some measurements and hacks to see about the performance and > >> scalability of PostgreSQL 9.3 on FreeBSD, sponsored by The FreeBSD > >> Foundation. > >> > >> The results are described in https://kib.kiev.ua/kib/pgsql_perf.pdf. > >> The uncommitted patches, referenced in the article, are available as > >> https://kib.kiev.ua/kib/pig1.patch.txt > >> https://kib.kiev.ua/kib/patch-2 > > > > A followup to the original paper. > > > > Most importantly, I identified the cause for the drop on the graph > > after the 30 clients, which appeared to be the debugging version > > of malloc(3) in libc. > > > > Also there are some updates on the patches. > > > > New version of the paper is available at > > https://www.kib.kiev.ua/kib/pgsql_perf_v2.0.pdf > > The changes are marked as 'update for version 2.0'. > > Would you mind trying a default (non-PRODUCTION) build, but with junk > filling turned off? > > adrian@adrian-hackbox:~ % ls -l /etc/malloc.conf > > lrwxr-xr-x 1 root wheel 10 Jun 24 04:37 /etc/malloc.conf -> junk:false > > That fixes almost all of the malloc debug performance issues that I > see without having to recompile. > > I'd like to know if you see any after that. OTOH, I have actually seen junk profiling _improve_ performance in certain cases as it forces promotion of allocated pages to superpages since all pages are dirtied. (I have a local hack that adds a new malloc option to explicitly memset() new pages allocated via mmap() that gives the same benefit without the junking overheadon each malloc() / free(), but it does increase physical RAM usage.) -- John Baldwin