From: Patric de Waha <lists@p-dw.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Two questions.. shared_buffers and long reader issue
Date: Wed, 11 Jul 2007 22:48:51 +0200
Message-ID: <46954233.4050807@p-dw.com> (raw)
In-Reply-To: <27288.1184173062@sss.pgh.pa.us>
References: <4694F8C5.2040005@p-dw.com>
<27288.1184173062@sss.pgh.pa.us>
Ok thanks.
iostat confirmed it's an IO bottleneck.
Will add some discs to the RAID unit.
Used 4 Raptor discs in Raid 10 until now.
best regards,
patric
Tom Lane wrote:
> Patric de Waha <lists@p-dw.com> writes:
>
>> Postgres is running on a dedicated server P4 DualCore, 4 Gig Ram.
>>
>
> When you don't even mention your disk hardware, that's a bad sign.
> In a database server the disk is usually more important than the CPU.
>
>
>> Why do long readers influence the rest of the transactions in such a
>> heavy way?
>> Any configuration changes which can help here?
>> Is it a disc-IO bottleneck thing?
>>
>
> Very possibly. Have you spent any time watching "vmstat 1" output
> to get a sense of whether your I/O is saturated?
>
>
>> WAL files are located on another disc than the dbase itself.
>>
>
> That's good, but it only relates to update performance not SELECT
> performance.
>
>
>> effective_cache_size = 5000
>>
>
> That's way too small for a 4G machine. You could probably stand to
> boost maintenance_work_mem too. However, neither of these have any
> immediate relationship to your problem.
>
> regards, tom lane
>
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: lists@p-dw.com
Subject: Re: Two questions.. shared_buffers and long reader issue
In-Reply-To: <46954233.4050807@p-dw.com>
* 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