X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B3BD6D8536 for ; Tue, 30 Aug 2005 13:42:17 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 03120-08 for ; Tue, 30 Aug 2005 16:42:12 +0000 (GMT) Received: from iad2.emailsrvr.com (iad2.emailsrvr.com [207.97.227.212]) by svr1.postgresql.org (Postfix) with ESMTP id 0B9A7D84DF for ; Tue, 30 Aug 2005 13:42:11 -0300 (ADT) Received: from [10.10.20.22] (unknown [216.94.157.147]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: remyb@medrium.com) by relay3.r3.iad.emailsrvr.com (SMTP Server) with ESMTP id 834F244C547; Tue, 30 Aug 2005 12:42:11 -0400 (EDT) In-Reply-To: <22550.1125419342@sss.pgh.pa.us> References: <22417.1125418551@sss.pgh.pa.us> <2fa5224f3e5af53598e33d115a2af980@medrium.com> <22550.1125419342@sss.pgh.pa.us> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable Cc: pgsql-performance@postgresql.org From: =?ISO-8859-1?Q?R=E9my_Beaumont?= Subject: Re: High load and iowait but no disk access Date: Tue, 30 Aug 2005 12:42:13 -0400 To: Tom Lane X-Mailer: Apple Mail (2.622) X-Virus-Scanned: OK X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 required=5 tests=[none] X-Spam-Level: X-Archive-Number: 200508/528 X-Sequence-Number: 14275 On 30-Aug-05, at 12:29, Tom Lane wrote: > =3D?ISO-8859-1?Q?R=3DE9my_Beaumont?=3D writes: >> On 30-Aug-05, at 12:15, Tom Lane wrote: >>> I know zip about NetApps, but doesn't the 8th column indicate pretty >>> steady disk reads? > >> Yes, but they are very low. > > Sure, but that's more or less what you'd expect if the thing is=20 > randomly > seeking all over the disk :-(. Just because it's a NetApp doesn't = mean > it's got zero seek time. Per NetApp, the disk utilization percentage they report does include=20 seek time, not just read/write operations. NetApp has been involved in trying to figure out what is going on and=20 their claim is that the NetApp filer is not IO bound. > > You did not say what sort of query this is, but I gather that it's=20 > doing > an indexscan on a table that is not at all in index order. Yes, most of those queries are doing an indexscan. It's a fresh=20 restore of our production database that we have vacuumed/analyzed. > Possible > solutions involve reverting to a seqscan (have you forced the planner=20= > to > choose an indexscan here, either directly or by lowering=20 > random_page_cost?) No. > or CLUSTERing the table by the index (which would need to be repeated > periodically, so it's not a great answer). Will try to cluster the tables and see if it changes anything. Still=20 doesn't explain what is going on with those seeks. Thanks, R=E9my > > regards, tom lane