pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <rjpeace@earthlink.net>
To: Guillaume Smet <guillaume.smet@openwide.fr>
To: pgsql-performance@postgresql.org
Subject: Re: weird performances problem
Date: Tue, 22 Nov 2005 07:53:46 -0500
Message-ID: <6.2.5.6.0.20051122074454.040fae60@earthlink.net> (raw)
In-Reply-To: <4382EB58.3020804@openwide.fr>
References: <437CC21D.8070402@openwide.fr>
	<dlugsf$25o5$1@news.hub.org>
	<4382EB58.3020804@openwide.fr>

If I understand your HW config correctly, all of the pg stuff is on 
the same RAID 10 set?

If so, give WAL its own dedicated RAID 10 set.  This looks like the 
old problem of everything stalling while WAL is being committed to HD.

This concept works for other tables as well.  If you have a tables 
that both want services at the same time, disk arm contention will 
drag performance into the floor when they are on the same HW set.

Profile your HD access and put tables that want to be accessed at the 
same time on different HD sets.  Even if you have to buy more HW to do it.

Ron


At 04:56 AM 11/22/2005, Guillaume Smet wrote:
>Qingqing Zhou wrote:
>>Someone is doing a massive *write* at this time, which makes your 
>>query *read* quite slow. Can you find out which process is doing write?
>
>Indexes should be in memory so I don't expect a massive write to 
>slow down the select queries. sdb is the RAID10 array dedicated to 
>our data so the postgresql process is the only one to write on it. 
>I'll check which write queries are running because there should 
>really be a few updates/inserts on our db during the day.
>
>On a four days log analysis, I have the following:
>SELECT  403,964
>INSERT  574
>UPDATE  393
>DELETE  26
>So it's not really normal to have a massive write during the day.
>
>Thanks for your help
>
>--
>Guillaume
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: Don't 'kill -9' the postmaster






view thread (14+ messages)  latest in thread

Message-ID: <6.2.5.6.0.20051122074454.040fae60@earthlink.net>
Permalink:  ../6.2.5.6.0.20051122074454.040fae60@earthlink.net/
Also on:    postgresql.org/message-id/6.2.5.6.0.20051122074454.040fae60@earthlink.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: rjpeace@earthlink.net, guillaume.smet@openwide.fr
  Subject: Re: weird performances problem
  In-Reply-To: <6.2.5.6.0.20051122074454.040fae60@earthlink.net>
  References: <437CC21D.8070402@openwide.fr> <dlugsf$25o5$1@news.hub.org> <4382EB58.3020804@openwide.fr> <6.2.5.6.0.20051122074454.040fae60@earthlink.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