Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 7CA2C632BC8 for ; Mon, 8 Feb 2010 11:25:32 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 00343-06-4 for ; Mon, 8 Feb 2010 15:24:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 75F0863261A for ; Mon, 8 Feb 2010 11:25:04 -0400 (AST) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Mon, 08 Feb 2010 09:25:02 -0600 Message-Id: <4B6FD868020000250002F084@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Mon, 08 Feb 2010 09:24:56 -0600 From: "Kevin Grittner" To: "Greg Smith *EXTERN*" , , "Albe Laurenz" Subject: Re: Linux I/O tuning: CFQ vs. deadline References: <4B6FDD26.9010106@2ndquadrant.com> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.468 tagged_above=-10 required=5 tests=AWL=0.131, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/120 X-Sequence-Number: 37541 "Albe Laurenz" wrote: > Greg Smith wrote: >> http://insights.oetiker.ch/linux/fsopbench/ > > That is interesting; particularly since I have made one quite > different experience in which deadline outperformed CFQ by a > factor of approximately 4. I haven't benchmarked it per se, but when we started using PostgreSQL on Linux, the benchmarks and posts I could find recommended deadline=elevator, so we went with that, and when the setting was missed on a machine it was generally found fairly quickly because people complained that the machine wasn't performing to expectations; changing this to deadline corrected the problem. > So I tried to look for differences, and I found two possible > places: > - My test case was read-only, our production system is > read-mostly. Yeah, our reads are typically several times our writes -- up to maybe 10 to 1. > - We did not have a RAID array, but a SAN box (with RAID inside). No SAN here, but if I recall correctly, this was mostly an issue on our larger arrays -- RAID 5 with dozens of spindles on a BBU hardware controller. Other differences between our environment and that of the benchmarks cited above: - We use SuSE Linux Enterprise Server, so we've been on *much* earlier kernel versions that this benchmark. - We've been using xfs, with noatime,nobarrier. I'll keep this in mind as something to try if we have problem performance in line with what that page describes, though.... -Kevin