Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty3an-00061a-H2 for pgsql-performance@arkaria.postgresql.org; Wed, 23 Jan 2013 16:54:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Ty3am-00074I-Ui for pgsql-performance@arkaria.postgresql.org; Wed, 23 Jan 2013 16:54:28 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty3al-00074C-PO for pgsql-performance@postgresql.org; Wed, 23 Jan 2013 16:54:27 +0000 Received: from qmta15.emeryville.ca.mail.comcast.net ([2001:558:fe2d:44:76:96:27:228]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty3ai-00008u-Qg for pgsql-performance@postgresql.org; Wed, 23 Jan 2013 16:54:27 +0000 Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta15.emeryville.ca.mail.comcast.net with comcast id rUSm1k0090EPchoAFUuLac; Wed, 23 Jan 2013 16:54:20 +0000 Received: from [192.168.1.176] ([69.142.185.164]) by omta01.emeryville.ca.mail.comcast.net with comcast id rUuG1k00c3ZEZL58MUuHP1; Wed, 23 Jan 2013 16:54:19 +0000 Message-ID: <510015A5.8060601@comcast.net> Date: Wed, 23 Jan 2013 11:53:57 -0500 From: AJ Weber User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: autovacuum fringe case? References: <50E4AAB1.9040902@optionshouse.com> <50EC6549.3090503@optionshouse.com> <50EC6742.4090303@optionshouse.com> <50EC743E.1040209@optionshouse.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1358960060; bh=wLSxF8u4sWUbhlEw5PP/Wx7G4JHOdlUgH5TBFomBYjQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=iIrv1kg9/VytA1UWNXHdknLndnpJ9YeZOihLLRbZ9IFO1z4EOdb/ZlWa5LnDxwhny QC0bMYj5ZY82YhMA+qX7rGfRCv5IdFFOXLjjRkkqkXFA6TpkiLbyzc8MLJB/6Mt/AZ Un/y/l2QVQEgcoMvKCtJhLlPOO0gStVSNsE+IFjm4AsPbdllVMf+/jZwt+MaWonWka z9Ves2opehVKyvj/SgIUSPbs13TBUf9zxtSqA64rSPfAD9j027SYgTEigLDOojm7GC FLf0EPqpVCK4LcHLO06p4iJqkB0mnsVJHpDw20oO/SYpztqRw8FVoOkXa4Z2lIw5Kt ZJt8xjdeXQJMQ== X-Pg-Spam-Score: -2.0 (--) 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 I have a server that is IO-bound right now (it's 4 cores, and top indicates the use rarely hits 25%, but the Wait spikes above 25-40% regularly). The 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 own host, but this is a production environment, so in the meantime... Is it possible that some spikes in IO could be attributable to the autovacuum process? Is there a way to check this theory? Would it be advisable (or even permissible to try/test) to disable autovacuum, and schedule a manual vacuumdb in the middle of the night, when this server is mostly-idle? Thanks for any tips. I'm in a bit of a jam with my limited hardware. -AJ -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance