Message-ID: <53F73F0F.3070808@optionshouse.com>
Date: Fri, 22 Aug 2014 08:01:03 -0500
From: Shaun Thomas <sthomas@optionshouse.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Scott Marlowe <scott.marlowe@gmail.com>, Josh Berkus <josh@agliodbs.com>
CC: Steve Crawford <scrawford@pinpointresearch.com>, Bruce Momjian
 <bruce@momjian.us>, "pgsql-performance@postgresql.org"
 <pgsql-performance@postgresql.org>, Mark Kirkwood
 <mark.kirkwood@catalyst.net.nz>, "Graeme B. Bell" <grb@skogoglandskap.no>
Subject: Re: Turn off Hyperthreading! WAS: 60 core performance with
 9.3
References: <53ACB190.2030206@catalyst.net.nz>	<53ECFD75.3060408@agliodbs.com>
	<53ED371D.109@catalyst.net.nz>
	<WM!14a45a34c8080927967621cff2751e173aba58b17a2748a7a628c8fd3be56f3c9596f20e774ed5df15c6863316278466!@asav-2.01.com>
	<53F4F36E.6050003@agliodbs.com>	<20140821024036.GB26706@momjian.us>
	<WM!a6def31edfeb44a0c2b33db4efa373ee781a1b82f342c0a03c2d35e540e65a0434c32d64b1353526644d086f6706ce42!@asav-3.01.com>
	<53F65E62.3020909@agliodbs.com>
	<CAOR=d=3RKfeHLqib-a-PmGMUuvrPQi8KFAVEi-7K4nm46P7m2g@mail.gmail.com>
	<WM!a927bb5fd4183fadc650b05372f3b203053c4a89878c724aa723f5d045348f1835912cff968187b6d88105bfd39ee6de!@asav-2.01.com>
	<53F677E8.7010603@agliodbs.com>	<53F67BD7.8030502@pinpointresearch.com>
	<WM!4d246cdb1603ab5fe4fca348eaeb8934c80f8f3fd56c07f508b49aeaf3c9bae0022250a79a2b44a566b5826a3b702fe8!@asav-3.01.com>
	<53F680D7.6030208@agliodbs.com>
 <CAOR=d=2qNfasTcHVVYD7qpA5o--RaVm14H2FUN4VhwRsY0Tupg@mail.gmail.com>
In-Reply-To: 
 <CAOR=d=2qNfasTcHVVYD7qpA5o--RaVm14H2FUN4VhwRsY0Tupg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
content-transfer-encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 08/22/2014 01:37 AM, Scott Marlowe wrote:

> I thought they were fixed in 3.8.something? We're running 3.8 on our
> production servers but IO is not an issue for us.

Yeah. 3.8 fixed a ton of issues that were plaguing us. There were still 
a couple patches I wanted that didn't get in until 3.11+, but the worst 
of the behavior was solved before that.

Bugs in kernel cache page aging algorithms are bad, m'kay?

-- 
Shaun Thomas
OptionsHouse, LLC | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance