Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty5bp-0003VQ-0e for pgsql-performance@arkaria.postgresql.org; Wed, 23 Jan 2013 19:03:41 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Ty5bo-0002L9-EV for pgsql-performance@arkaria.postgresql.org; Wed, 23 Jan 2013 19:03:40 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty5bm-0002JX-KZ for pgsql-performance@postgresql.org; Wed, 23 Jan 2013 19:03:38 +0000 Received: from mail-la0-f41.google.com ([209.85.215.41]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty5bh-0002FD-RM for pgsql-performance@postgresql.org; Wed, 23 Jan 2013 19:03:38 +0000 Received: by mail-la0-f41.google.com with SMTP id fo12so3705750lab.14 for ; Wed, 23 Jan 2013 11:03:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=5LnD19hAK5X81DrjFG4dhXsvv2WKo30D1yE2tkeS5zM=; b=lFgVsU39mzm3smLoQ9hFJPlUagC3Q+1uGVZTRb1bFL0Uq97uMMWf8dvcuzxnCwnBjf 29aDompIsSDk87g1yvZhVCO00EkI0zqsIvX5cQHwWvflLZuZbiUVlwujU4xoJXYV2+aN RSwO7Jw3qluBXvstqvZa980dL5L3bp/3+DgoDmiTFHjZx+Ufiq3EYH9BPpgFaBKJ1a0R q6PjYzBVpWQktxDDPyjKsBM2Cy6up7uFLhb+Nhk0aT3nlBa2d30IVkLlvVj/BAGTsb34 xTHZAeFNw+V5KiVnCk3/aY/+rsdKpJ0Qhfx6dM2H+viNM1oOF4AS3ZN1Up7oiTBHjqU6 h/RA== X-Received: by 10.112.24.199 with SMTP id w7mr398077lbf.102.1358967812292; Wed, 23 Jan 2013 11:03:32 -0800 (PST) Received: from [10.229.96.77] ([213.87.136.105]) by mx.google.com with ESMTPS id if8sm8769265lab.1.2013.01.23.11.03.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jan 2013 11:03:31 -0800 (PST) References: <50E4AAB1.9040902@optionshouse.com> <50EC6549.3090503@optionshouse.com> <50EC6742.4090303@optionshouse.com> <50EC743E.1040209@optionshouse.com> <510015A5.8060601@comcast.net> Mime-Version: 1.0 (1.0) In-Reply-To: <510015A5.8060601@comcast.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <3EB000F8-7FC6-4693-9451-8A263DBD0452@gmail.com> Cc: "pgsql-performance@postgresql.org" X-Mailer: iPhone Mail (10A551) From: Evgeniy Shishkin Subject: Re: autovacuum fringe case? Date: Wed, 23 Jan 2013 23:03:25 +0400 To: AJ Weber X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 23.01.2013, at 20:53, AJ Weber wrote: > I have a server that is IO-bound right now (it's 4 cores, and top indicat= es the use rarely hits 25%, but the Wait spikes above 25-40% regularly). T= he server is running postgresql 9.0 and tomcat 6. As I have mentioned in a= previous thread, I can't alter the hardware to add disks unfortunately, so= I'm going to try and move postgresql off this application server to its ow= n host, but this is a production environment, so in the meantime... >=20 > Is it possible that some spikes in IO could be attributable to the autova= cuum process? Is there a way to check this theory? >=20 Try iotop > Would it be advisable (or even permissible to try/test) to disable autova= cuum, and schedule a manual vacuumdb in the middle of the night, when this = server is mostly-idle? >=20 > Thanks for any tips. I'm in a bit of a jam with my limited hardware. >=20 > -AJ >=20 >=20 >=20 > --=20 > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance