Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id CE0A9B5DCC9 for ; Mon, 5 Sep 2011 16:07:50 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 23763-03 for ; Mon, 5 Sep 2011 19:07:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from marajade.localdomain (97-64-237-59.client.mchsi.com [97.64.237.59]) by mail.postgresql.org (Postfix) with ESMTP id 15813B5DC9D for ; Mon, 5 Sep 2011 16:07:43 -0300 (ADT) Received: from [192.168.1.116] (173-31-201-111.client.mchsi.com [173.31.201.111]) (Authenticated sender: andy) by marajade.localdomain (Postfix) with ESMTPA id 5A29443B53; Mon, 5 Sep 2011 14:07:43 -0500 (CDT) Message-ID: <4E651DFE.805@squeakycode.net> Date: Mon, 05 Sep 2011 14:07:42 -0500 From: Andy Colson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110707 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Scott Marlowe CC: Gerhard Wohlgenannt , Tomas Vondra , pgsql-performance@postgresql.org, Heinz-Peter Lang , Gerhard Wohlgenannt , "Weichselbraun, Albert" Subject: Re: Sudden drop in DBb performance References: <4E61D6B4.9090804@ai.wu.ac.at> <33fadeb6ac1bade5ef01bd08d1fd7807.squirrel@sq.gransy.com> <4E64D3D3.8000205@squeakycode.net> <4E64D7EA.3010704@ai.wu.ac.at> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.918 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RDNS_DYNAMIC=0.982 X-Spam-Level: X-Archive-Number: 201109/47 X-Sequence-Number: 44823 On 09/05/2011 01:45 PM, Scott Marlowe wrote: > On Mon, Sep 5, 2011 at 8:08 AM, Gerhard Wohlgenannt wrote: >> Below please find the results of vmstat 2 over some periode of time .. with >> normal database / system load. >> 2 1 1344204 240924 104156 31462484 350 0 1906 234 3687 4512 12 3 77 9 > > Your IO Wait is actually pretty high. On an 8 core machine, 12.5% > means one core is doing nothing but waiting for IO. > My server is 2-core, so these numbers looked fine by me. I need to remember core count when I look at these. So the line above, for 2 core's would not worry me a bit, but on 8 cores, it pretty much means one core was pegged (with 9% wait? Or is it one core was pegged, and another was 72% io wait?) I have always loved the vmstat output, but its starting to get confusing when you have to take core's into account. (And my math was never strong in the first place :-) ) Good catch, thanks Scott. -Andy