From owner-freebsd-current@freebsd.org  Fri Jun  3 17:26:44 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6668AB69BDD;
 Fri,  3 Jun 2016 17:26:44 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 D834E196D;
 Fri,  3 Jun 2016 17:26:43 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u53HQYuo001539
 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
 Fri, 3 Jun 2016 20:26:34 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u53HQYuo001539
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id u53HQXfA001538;
 Fri, 3 Jun 2016 20:26:33 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Fri, 3 Jun 2016 20:26:33 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: Alan Somers <asomers@freebsd.org>
Cc: Alan Cox <alc@rice.edu>, John Baldwin <jhb@freebsd.org>, alc@freebsd.org, 
 Adrian Chadd <adrian@freebsd.org>,
 freebsd-current <freebsd-current@freebsd.org>, performance@freebsd.org,
 "current@freebsd.org" <current@freebsd.org>
Subject: Re: PostgreSQL performance on FreeBSD
Message-ID: <20160603172633.GY38613@kib.kiev.ua>
References: <20140627125613.GT93733@kib.kiev.ua>
 <201408121409.40653.jhb@freebsd.org>
 <CAJUyCcMAw-etXh3gByLE_xpLOkO=LZihUVVfzgAtSb809QcPWA@mail.gmail.com>
 <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu>
 <CAOtMX2iH7=AAvHWg7xw=u5nyO6ANF1J3uVMKPsf+V=PYBEumvA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOtMX2iH7=AAvHWg7xw=u5nyO6ANF1J3uVMKPsf+V=PYBEumvA@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 17:26:44 -0000

On Fri, Jun 03, 2016 at 09:29:16AM -0600, Alan Somers wrote:
> I notice that, with the exception of the VM_PHYSSEG_MAX change, these
> patches never made it into head or ports.  Are they unsuitable for low
> core-count machines, or is there some other reason not to commit them?
>  If not, what would it take to get these into 11.0 or 11.1 ?

The fast page fault handler was redesigned and committed in r269728
and r270011 (with several follow-ups).
Instead of lock-less buffer queues iterators, Jeff changed buffer allocator
to use uma, see r289279.  Other improvement to the buffer cache was
committed as r267255.

What was not committed is the aggressive pre-population of the phys objects
mem queue, and a knob to further split NUMA domains into smaller domains.
The later change is rotten.

In fact, I think that with that load, what you would see right now on
HEAD, is the contention on vm_page_queue_free_mtx.  There are plans to
handle it.