pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: AJ Weber <aweber@comcast.net>
To: pgsql-performance@postgresql.org
Subject: autovacuum fringe case?
Date: Wed, 23 Jan 2013 11:53:57 -0500
Message-ID: <510015A5.8060601@comcast.net> (raw)
In-Reply-To: <CABvEAQs7cRUH9PLHyTo-F+0t8=iKgX8N3ZSfCuzeSWXBJ9hM3w@mail.gmail.com>
References: <50E4AAB1.9040902@optionshouse.com>
	<B994348460014EC7BA65F310E9D30EBD@BERNICE>
	<50EC6549.3090503@optionshouse.com>
	<CAOR=d=2g4iH+4U2Dkn2EZtTnZrescxp+MW10zehVUzX6a5GXSA@mail.gmail.com>
	<50EC6742.4090303@optionshouse.com>
	<CAOR=d=0R1GPVfhhy9w2+j=czNvgtbA519rY6-Or6sNegvQmdFQ@mail.gmail.com>
	<50EC743E.1040209@optionshouse.com>
	<CABvEAQs7cRUH9PLHyTo-F+0t8=iKgX8N3ZSfCuzeSWXBJ9hM3w@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

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



view thread (7+ messages)  latest in thread

Message-ID: <510015A5.8060601@comcast.net>
Permalink:  ../510015A5.8060601@comcast.net/
Also on:    postgresql.org/message-id/510015A5.8060601@comcast.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: aweber@comcast.net
  Subject: Re: autovacuum fringe case?
  In-Reply-To: <510015A5.8060601@comcast.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox