From owner-freebsd-performance@freebsd.org Fri Jun 3 15:29:18 2016 Return-Path: Delivered-To: freebsd-performance@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 D5543B69805 for ; Fri, 3 Jun 2016 15:29:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B51EA17F8 for ; Fri, 3 Jun 2016 15:29:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AD948B69802; Fri, 3 Jun 2016 15:29:18 +0000 (UTC) Delivered-To: performance@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 ACB8CB69800; Fri, 3 Jun 2016 15:29:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7228017EE; Fri, 3 Jun 2016 15:29:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x242.google.com with SMTP id x130so17698796oia.3; Fri, 03 Jun 2016 08:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=R8j3nmiecM0IH9E9VcTwWXH3zVzgN1N9NL7TEGAnt7w=; b=ixob1NJUyj3njv9m6BAEO+3izmb17p3tN8uAcxkq08KZJ6r+kGHlfUQjIamym28RV+ z0I8BDbD1ynbI0/pkM52fbU6d8Tdo7B+Q2VSjr2+Z7ML1KmJNYQweUbT1wA57DP9VqB/ BM7wD6eEeSzBuj5eAVtNt0CXO7qiLIK7gZFp68VpchTe4Ir79BWucOpqrJE5UEcbNEEQ 8t+wPYwTFd5tgRkV+FyEaPo9Vu7P0N0JB92iq8kGqv8gGGNQPN7x2FKrlyrUdIlUe+FC 1R0qItA3kDgPaaM7EDBCciumdbsnzJBwRiPUVC5fBsZZyrX+860I/1UYH8aXYKFtBUJ/ yqmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=R8j3nmiecM0IH9E9VcTwWXH3zVzgN1N9NL7TEGAnt7w=; b=ITZpQMtnjXHVLG9hHTp/0TsarjSCG8vpN5LbyhPwImdOx4fDMRS0sjnx5a/SgCpVZj G29J84irKakymdetSH7NRbyAK9PIcHy2F+u2T6AEyj05o1AuXE+kJFeU+2u3iayI1Aet i3bjAlbLONPlbV3BS0cGxBtkXJ/+H05M6GwaFEL64JSB267J6Y1K54tmVt/KscVekYgc Mp4vDYroppmE/081qAiSK68DYk/jO7QAmr0jvdZaOrTgitQWS9W2KXKDY0oPVXzXWYhC Qn1CCfdQiJLdJseJNaklb/zpBImnRfL4CC69Vo5vee9MYhvj8UhaVuelzXIkFCRkKyss lFQw== X-Gm-Message-State: ALyK8tItL05yk6dpGYA73CVD6Xf2bWfUjj0E6F9nYfXptxldpQWXSwyzk+J/0964DPyIRu2unSGgcg0nznyTuQ== X-Received: by 10.157.29.177 with SMTP id y46mr2129684otd.164.1464967757168; Fri, 03 Jun 2016 08:29:17 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.202.4.200 with HTTP; Fri, 3 Jun 2016 08:29:16 -0700 (PDT) In-Reply-To: <53ECFDC8.1070200@rice.edu> References: <20140627125613.GT93733@kib.kiev.ua> <201408121409.40653.jhb@freebsd.org> <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu> From: Alan Somers Date: Fri, 3 Jun 2016 09:29:16 -0600 X-Google-Sender-Auth: tL4nuLltg764HZURpLYW5yVGUBo Message-ID: Subject: Re: PostgreSQL performance on FreeBSD To: Alan Cox Cc: John Baldwin , alc@freebsd.org, Konstantin Belousov , Adrian Chadd , freebsd-current , performance@freebsd.org, "current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Fri, 03 Jun 2016 15:43:10 +0000 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 15:29:18 -0000 On Thu, Aug 14, 2014 at 12:19 PM, Alan Cox wrote: > On 08/14/2014 10:47, John Baldwin wrote: >> On Wednesday, August 13, 2014 1:00:22 pm Alan Cox wrote: >>> On Tue, Aug 12, 2014 at 1:09 PM, John Baldwin wrote: >>> >>>> 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, >>> >>> A couple small steps have been taken toward eliminating the need for this >>> hack: the addition of the "page size index" field to struct vm_page and the >>> addition of a similarly named parameter to pmap_enter(). However, at the >>> moment, the only tangible effect is in the automatic prefaulting by >>> mmap(2). Instead of establishing 96 4KB page mappings, the automatic >>> prefaulting establishes 96 page mappings whose size is determined by the >>> size of the physical pages that it finds in the vm object. So, the >>> prefaulting overhead remains constant, but the coverage provided by the >>> automatic prefaulting will vary with the underlying page size. >> Yes, I think what we might actually want is what I mentioned in person at >> BSDCan: some sort of flag to mmap() that malloc() could use to assume that any >> reservations are fully used when they are reserved. This would avoid the need >> to wait for all pages to be dirtied before promotion provides a superpage >> mapping and would avoid demotions while still allowing the kernel to gracefully >> fall back to regular pages if a reservation can't be made. >> > > I agree. 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 ? -Alan From owner-freebsd-performance@freebsd.org Fri Jun 3 17:26:44 2016 Return-Path: Delivered-To: freebsd-performance@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 85519B69BE2 for ; Fri, 3 Jun 2016 17:26:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6BA51196F for ; Fri, 3 Jun 2016 17:26:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6771CB69BDF; Fri, 3 Jun 2016 17:26:44 +0000 (UTC) Delivered-To: performance@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 To: Alan Somers Cc: Alan Cox , John Baldwin , alc@freebsd.org, Adrian Chadd , freebsd-current , performance@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> <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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. From owner-freebsd-performance@freebsd.org Fri Jun 3 17:13:21 2016 Return-Path: Delivered-To: freebsd-performance@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 EFBE4B697BE for ; Fri, 3 Jun 2016 17:13:21 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DB3E21F16 for ; Fri, 3 Jun 2016 17:13:21 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DAABAB697BC; Fri, 3 Jun 2016 17:13:21 +0000 (UTC) Delivered-To: performance@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 D9D86B697BA; Fri, 3 Jun 2016 17:13:21 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5DE91F14; Fri, 3 Jun 2016 17:13:21 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1464973993043178.94664369864552; Fri, 3 Jun 2016 10:13:13 -0700 (PDT) Date: Fri, 03 Jun 2016 10:13:12 -0700 From: Matthew Macy To: "Alan Somers" Cc: "Alan Cox" , "John Baldwin" , "" , "Konstantin Belousov" , "Adrian Chadd" , "freebsd-current" , "" , "current@freebsd.org" Message-ID: <15517412419.c1e94b0289020.2514233510095214876@nextbsd.org> In-Reply-To: References: <20140627125613.GT93733@kib.kiev.ua> <201408121409.40653.jhb@freebsd.org> <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu> Subject: Re: PostgreSQL performance on FreeBSD MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-Mailman-Approved-At: Fri, 03 Jun 2016 17:40:36 +0000 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 17:13:22 -0000 > >>> A couple small steps have been taken toward eliminating the need for this > >>> hack: the addition of the "page size index" field to struct vm_page and the > >>> addition of a similarly named parameter to pmap_enter(). However, at the > >>> moment, the only tangible effect is in the automatic prefaulting by > >>> mmap(2). Instead of establishing 96 4KB page mappings, the automatic > >>> prefaulting establishes 96 page mappings whose size is determined by the > >>> size of the physical pages that it finds in the vm object. So, the > >>> prefaulting overhead remains constant, but the coverage provided by the > >>> automatic prefaulting will vary with the underlying page size. > >> Yes, I think what we might actually want is what I mentioned in person at > >> BSDCan: some sort of flag to mmap() that malloc() could use to assume that any > >> reservations are fully used when they are reserved. This would avoid the need > >> to wait for all pages to be dirtied before promotion provides a superpage > >> mapping and would avoid demotions while still allowing the kernel to gracefully > >> fall back to regular pages if a reservation can't be made. > >> > > > > I agree. > > 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 ? > I think the two big issues are: a) there's a lot more work that needs to be done b) Adrian has had a lot of other things on his plate in the meantime. Adrian is hoping to get back to it post 11.0-RELEASE. From owner-freebsd-performance@freebsd.org Fri Jun 3 17:55:55 2016 Return-Path: Delivered-To: freebsd-performance@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 BC59BB6846E for ; Fri, 3 Jun 2016 17:55:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A24FC1CF7 for ; Fri, 3 Jun 2016 17:55:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9ACC2B6846A; Fri, 3 Jun 2016 17:55:55 +0000 (UTC) Delivered-To: performance@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 99E20B68468; Fri, 3 Jun 2016 17:55:55 +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 435C91CF5; Fri, 3 Jun 2016 17:55:55 +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 u53HtlY6008405 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 3 Jun 2016 20:55:47 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u53HtlY6008405 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u53HtkQc008398; Fri, 3 Jun 2016 20:55:46 +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:55:46 +0300 From: Konstantin Belousov To: Alan Somers Cc: Alan Cox , John Baldwin , alc@freebsd.org, Adrian Chadd , freebsd-current , performance@freebsd.org, "current@freebsd.org" Subject: Re: PostgreSQL performance on FreeBSD Message-ID: <20160603175546.GZ38613@kib.kiev.ua> References: <20140627125613.GT93733@kib.kiev.ua> <201408121409.40653.jhb@freebsd.org> <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu> <20160603172633.GY38613@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 17:55:55 -0000 On Fri, Jun 03, 2016 at 11:29:13AM -0600, Alan Somers wrote: > On Fri, Jun 3, 2016 at 11:26 AM, Konstantin Belousov > wrote: > > 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. > > Thanks for the update. Is it still recommended to enable the > multithreaded pagedaemon? Single-threaded pagedaemon cannot maintain the good system state even on non-NUMA systems, if machine has large memory. This was the motivation for the NUMA domain split patch. So yes, to get better performance you should enable VM_NUMA_ALLOC option. Unfortunately, there were some code changes of quite low quality which resulted in the NUMA-enabled system to randomly fail with NULL pointer deref in the vm page alloc path. Supposedly that was fixed, but you should try that yourself. One result of the mentioned changes was that nobody used/tested NUMA-enabled systems under any significant load, for quite long time. From owner-freebsd-performance@freebsd.org Fri Jun 3 17:29:15 2016 Return-Path: Delivered-To: freebsd-performance@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 70BCBB69CF8 for ; Fri, 3 Jun 2016 17:29:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 503841B86 for ; Fri, 3 Jun 2016 17:29:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 48A57B69CF5; Fri, 3 Jun 2016 17:29:15 +0000 (UTC) Delivered-To: performance@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 47CF9B69CF3; Fri, 3 Jun 2016 17:29:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x244.google.com (mail-oi0-x244.google.com [IPv6:2607:f8b0:4003:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CE151B82; Fri, 3 Jun 2016 17:29:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x244.google.com with SMTP id f12so62123oig.0; Fri, 03 Jun 2016 10:29:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=0T/M7FVnkzUYPYnLcFH3kPoXbFfV5oq2CaxWWIOwniw=; b=iGIXdhv5SmpqGrEEZCVFu3LD7ILg0qyFsCnjvoyyCUNVGgoPIMXmiHZ6InzVvZZYe8 z5a8MAEbqW6kDWoFPXaDNL9L80otHF35ecgtT1o1q3MnQNoITA92bVs22Tygpbfp6N1j QDnND2TfE5KebI3FMLz8eRhwirJSilh2NsYQ6j41RkCfNpS4+lfvUPSkNYlSDOqOidgf /a2X03PKdqti2bRyXahVj5ApTk0eiTWy4MrEHfU4zcHDLzCtEDl59o6sEzmu7v9Tyrub MrQxcfw/aJoOh2rD//QDuR/3dBuC5Jl0KHCtR1F7JPT8RVFlgg9UIoO8KKf3UEbYB8zY H4eQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=0T/M7FVnkzUYPYnLcFH3kPoXbFfV5oq2CaxWWIOwniw=; b=igA1+VTQfwzuxxL7zAOP6PBtBmvzHeP3xpE+CFaUSo5Xh20mEenrkgr+ggGdPBNSqA 9GipXy02AexaYH40qYsdnBgNqSkwYbWxMsmXIfJBsi5vQaV4zS7Yn/PLbcTTpD6wLvQK 6xHEel4tASrT/BqaFc378nMW9EbtOzEKVdk2ntn7U4NLrUCNjnO6dckswQjwPNZIieDf 5L6ITQUug8VXqRCgLElLk2B/heOUVp3V4oI4R9rmdcjc9xBOYTyyvp9IXbNoiIQmgkTJ YTthWQ131paVXPDLdAWZ/9tKpjJwzhlJAz3tcMAnzNP4SQaxe4hSGNyr29Ro5fAbYw2C 7UBQ== X-Gm-Message-State: ALyK8tI47ZOfVDuEd3EV+5y0D/nhK75H8/aws4EuHumEnDYHoPgKQ/13caFgRh1dBIxBTl+CJjRYlThn70aqtw== X-Received: by 10.202.212.19 with SMTP id l19mr2524272oig.182.1464974954443; Fri, 03 Jun 2016 10:29:14 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.202.4.200 with HTTP; Fri, 3 Jun 2016 10:29:13 -0700 (PDT) In-Reply-To: <20160603172633.GY38613@kib.kiev.ua> References: <20140627125613.GT93733@kib.kiev.ua> <201408121409.40653.jhb@freebsd.org> <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu> <20160603172633.GY38613@kib.kiev.ua> From: Alan Somers Date: Fri, 3 Jun 2016 11:29:13 -0600 X-Google-Sender-Auth: BEUIntNPI2bGuyinfCcreiWpry4 Message-ID: Subject: Re: PostgreSQL performance on FreeBSD To: Konstantin Belousov Cc: Alan Cox , John Baldwin , alc@freebsd.org, Adrian Chadd , freebsd-current , performance@freebsd.org, "current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Fri, 03 Jun 2016 18:26:32 +0000 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 17:29:15 -0000 On Fri, Jun 3, 2016 at 11:26 AM, Konstantin Belousov wrote: > 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. Thanks for the update. Is it still recommended to enable the multithreaded pagedaemon? From owner-freebsd-performance@freebsd.org Fri Jun 3 18:27:24 2016 Return-Path: Delivered-To: freebsd-performance@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 066B7B68EAE for ; Fri, 3 Jun 2016 18:27:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D89121707 for ; Fri, 3 Jun 2016 18:27:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D150CB68EA8; Fri, 3 Jun 2016 18:27:23 +0000 (UTC) Delivered-To: performance@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 CFCD3B68EA6; Fri, 3 Jun 2016 18:27:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 982451702; Fri, 3 Jun 2016 18:27:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x230.google.com with SMTP id p194so83054702iod.1; Fri, 03 Jun 2016 11:27:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KYSrGvKkDPpfkFFqk0QJVYR360zHdOdndByM16Z1gQc=; b=gYggnWB0Cd8noDUdzPNp1ckdilRl0/FPwbqnT26rDflwYzSCwqm1JcDx9dkzNlUmIg /V+di/CnlTf8vVLpVbQAp4OFVArWUZwaqLbn6JV69L7COoFOI1y9/ewmPE/H5YWUmgWM q4Y21zF9H9yhOBA3T+R/g0Pp0yXj202V4gDTx58+lwNPkRtSrQP5d/KZVNbDBgSM8es4 0KyPeguj9tOUty8H6vqhd8Y24a5RK1/GYtipz6c5uTYh5PdfucbHx3wR+zJ/J+kQ3eCo JE+6lLo6xPy/HEd8x38OusxC30i2HSnmhJTaXrDwWxXcrcNMh5xioNIAT0Hw09x5b7p9 mHUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=KYSrGvKkDPpfkFFqk0QJVYR360zHdOdndByM16Z1gQc=; b=LD+49TE2rWlO4Ck0WrOdsYdYSHL9BEPmIRP24okgb8iZR7ulqq1E+tv8svOhWdssRY gwk4IWYyoGzyYkM+D2Pwe1hC6NvllXBd+xSHuhAPVBX997yiq49WPn6rULdePoPgaRXQ d1aVrkuBGsLHuTUZZJjpjC1tg8LGTPFjJo9sRsCEzBP3GVtvGNK488EvHf0ixseZBpZl orKbicdZ91GLsEi/ZDDCHW2hm1oKsqc+U3kX5UiFe2yPIfKB6K3Yxa47nx/i8Ydh0/TA YkHBEd35pL2DD5HguDWdRfyXssCMsstqmQUYqzh/CQh3fBYVHrtqnTvoX5s+bVghghtp IPyQ== X-Gm-Message-State: ALyK8tL+kRhZjbYNGx/7RX1b5Cw6papnfiQKYiB+4SuNFa40/F65TywbDIYfgwkGEueAn58YPBBdFJiNvoR4mQ== X-Received: by 10.36.81.79 with SMTP id s76mr1333740ita.71.1464978442929; Fri, 03 Jun 2016 11:27:22 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.113.3 with HTTP; Fri, 3 Jun 2016 11:27:21 -0700 (PDT) In-Reply-To: <20160603175546.GZ38613@kib.kiev.ua> References: <20140627125613.GT93733@kib.kiev.ua> <201408121409.40653.jhb@freebsd.org> <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu> <20160603172633.GY38613@kib.kiev.ua> <20160603175546.GZ38613@kib.kiev.ua> From: Adrian Chadd Date: Fri, 3 Jun 2016 11:27:21 -0700 X-Google-Sender-Auth: gR6yv1SFYVzC9Sqq7mfFCO6qbuI Message-ID: Subject: Re: PostgreSQL performance on FreeBSD To: Konstantin Belousov Cc: Alan Somers , Alan Cox , John Baldwin , Alan Cox , freebsd-current , performance@freebsd.org, "current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 18:27:24 -0000 On 3 June 2016 at 10:55, Konstantin Belousov wrote: > On Fri, Jun 03, 2016 at 11:29:13AM -0600, Alan Somers wrote: >> On Fri, Jun 3, 2016 at 11:26 AM, Konstantin Belousov >> wrote: >> > 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. >> >> Thanks for the update. Is it still recommended to enable the >> multithreaded pagedaemon? > > Single-threaded pagedaemon cannot maintain the good system state even > on non-NUMA systems, if machine has large memory. This was the motivation > for the NUMA domain split patch. So yes, to get better performance you > should enable VM_NUMA_ALLOC option. > > Unfortunately, there were some code changes of quite low quality which > resulted in the NUMA-enabled system to randomly fail with NULL pointer > deref in the vm page alloc path. Supposedly that was fixed, but you > should try that yourself. One result of the mentioned changes was that > nobody used/tested NUMA-enabled systems under any significant load, for > quite long time. The iterator bug was fixed, so it still behaves like it used to if NUMA is enabled circa what, freebsd-9? If you'd like that older behavior, you can totally flip back to the global policy being round-robin only, and it's then a glorified, configurable-at-runtime no-op. The difference now is that you can tickle imbalances if you have too many processes that need pages from a specific domain instead of round robin, because the underlying tracking mechanisms still assume a single global pool and global method of cleaning things. That and the other NUMA stuff is something to address in -12. -adrian From owner-freebsd-performance@freebsd.org Fri Jun 3 18:29:06 2016 Return-Path: Delivered-To: freebsd-performance@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 8E6AFB69006 for ; Fri, 3 Jun 2016 18:29:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6B9961941 for ; Fri, 3 Jun 2016 18:29:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 673F8B69002; Fri, 3 Jun 2016 18:29:06 +0000 (UTC) Delivered-To: performance@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 668E0B69001; Fri, 3 Jun 2016 18:29:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A02C193F; Fri, 3 Jun 2016 18:29:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x229.google.com with SMTP id k19so69317676ioi.3; Fri, 03 Jun 2016 11:29:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KKzenDbUPi7frWUiQAS7wiF9ApSqtIvscKaM1T0WR4o=; b=P46QW1thYnfpKsI/nzfsePIFB+NbaHpcwS74Kg5S1lxGc9L87ka+hKjYXE8bz/Ynb6 FDfjyJp+5BGgblh7zAH8GXREKPUVirfqe0K0soAa01YcmbNVtzKAVvI3gc/GRm8OmGgA VueE8Kss9rI8/qR5q5gv5TOzxovMmZZ6jkfbn+0/HeDIEvoOk9NNEiY0+hCVsoqoR6By isTMlj8hLklaYasfUqhZnyMY3OPQFt4VP+F3LBuySa1rzCXRdzWXEYofs1br4Dem9952 MOMWfWDukHEXTFliy+pRSgpvK5wKK3nY2R12of0pCyUQHVIwYZOpxWMBmRS2gUD37nej zgYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=KKzenDbUPi7frWUiQAS7wiF9ApSqtIvscKaM1T0WR4o=; b=INu6MMsgXjdkN1KQ9zuMxGGYwib6SSr8Vtg6z5pInCtgpuYbs3ETEKtAmimD81v0II 37PO+zEYgy913y32Rx/q+Lom0wI6eqcr2dGV6vulS/9mfgrJmO4W8vp+J7K06xfyM+FH kCB4Yc3k7vPi0pQIhKrQhjQ/R8eaFGcawG72NCqlHNvcVCjDsutdJJBlv15+XDYx5Pt5 5PyPzIdQsYfyIrJWdMUyRMJPa63xXSLDIcj5X+AfG+SxCB5n6Lj8Tz/v47avkyd1e2sR bzCqVQ+NcQNswv+cEV9m/obzwwPXUqzSMu6ZNHO9fbMdg9mY4giyj7VDH8M2PfvgjM5A m6eQ== X-Gm-Message-State: ALyK8tJ8Hj04ZRM8SI5P3y2xMtN58mef/5LHTc6lbhCo3a2hD+eIlWJG3oceQVISA0HWVBWXGQtcbOqoz9Kirg== X-Received: by 10.36.92.199 with SMTP id q190mr1399491itb.25.1464978544648; Fri, 03 Jun 2016 11:29:04 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.113.3 with HTTP; Fri, 3 Jun 2016 11:29:03 -0700 (PDT) In-Reply-To: References: <20140627125613.GT93733@kib.kiev.ua> <201408121409.40653.jhb@freebsd.org> <201408141147.45698.jhb@freebsd.org> <53ECFDC8.1070200@rice.edu> <20160603172633.GY38613@kib.kiev.ua> <20160603175546.GZ38613@kib.kiev.ua> From: Adrian Chadd Date: Fri, 3 Jun 2016 11:29:03 -0700 X-Google-Sender-Auth: e_d2MJ3KDnc3yC014PpWP85tZWA Message-ID: Subject: Re: PostgreSQL performance on FreeBSD To: Konstantin Belousov Cc: Alan Somers , Alan Cox , John Baldwin , Alan Cox , freebsd-current , performance@freebsd.org, "current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 18:29:06 -0000 On 3 June 2016 at 11:27, Adrian Chadd wrote: > That and the other NUMA stuff is something to address in -12. And, I completely welcome continued development in NUMA scaling in combination with discussion. The iterator changes I committed are a more generic version of a patch people were applying on top of -10 and -head for at least what, three years now? Maybe more if -9 also just did round-robin and not first-touch? -adrian From owner-freebsd-performance@freebsd.org Sat Jun 4 14:08:41 2016 Return-Path: Delivered-To: freebsd-performance@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 AE079B6969C for ; Sat, 4 Jun 2016 14:08:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 99ED31D51 for ; Sat, 4 Jun 2016 14:08:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 912DDB69699; Sat, 4 Jun 2016 14:08:41 +0000 (UTC) Delivered-To: performance@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 90830B69697; Sat, 4 Jun 2016 14:08:41 +0000 (UTC) (envelope-from jhb@freebsd.org) 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 6F7061D4B; Sat, 4 Jun 2016 14:08:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 71FADB917; Sat, 4 Jun 2016 10:08:39 -0400 (EDT) From: John Baldwin To: Adrian Chadd Cc: Konstantin Belousov , Alan Somers , Alan Cox , Alan Cox , freebsd-current , performance@freebsd.org, "current@freebsd.org" Subject: Re: PostgreSQL performance on FreeBSD Date: Fri, 03 Jun 2016 11:53:15 -0700 Message-ID: <1603235.2ShtoCfSqO@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <20140627125613.GT93733@kib.kiev.ua> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Sat, 04 Jun 2016 10:08:39 -0400 (EDT) X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 14:08:41 -0000 On Friday, June 03, 2016 11:29:03 AM Adrian Chadd wrote: > On 3 June 2016 at 11:27, Adrian Chadd wrote: > > > That and the other NUMA stuff is something to address in -12. > > And, I completely welcome continued development in NUMA scaling in > combination with discussion. The iterator changes I committed are a > more generic version of a patch people were applying on top of -10 and > -head for at least what, three years now? Maybe more if -9 also just > did round-robin and not first-touch? 8 and 9 did first-touch. Only 10 did round-robin. -- John Baldwin