From: Doug Y <dylists@ptd.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning shared_buffers with ipcs ?
Date: Fri, 15 Oct 2004 17:18:12 -0400
Message-ID: <41703E94.3030800@ptd.net> (raw)
In-Reply-To: <20131.1097870008@sss.pgh.pa.us>
References: <416FF5BF.8060200@ptd.net>
<10905.1097862665@sss.pgh.pa.us>
<41701C35.4060808@ptd.net>
<20131.1097870008@sss.pgh.pa.us>
Tom Lane wrote:
>Doug Y <dylists@ptd.net> writes:
>
>
>>Tom Lane wrote:
>>
>>
>>>This might tell you something about how many concurrent backends you've
>>>used, but nothing about how many shared buffers you need.
>>>
>>>
>>>
>>Thats strange, I know I've had more than 4 concurrent connections on
>>that box... (I just checked and there were at least a dozen).
>>
>>
>
>There is more than one per-backend semaphore per semaphore set, 16 per
>set if memory serves; so the ipcs evidence points to a maximum of
>between 49 and 64 concurrently active backends. It's not telling you a
>darn thing about appropriate shared_buffers settings, however.
>
>
>
>>A mirror DB with the same config also has the same basic output from
>>ipcs, except that it has times for 11 of the 17 arrays slots and most
>>of them are the time when we do our backup dump (which makes sense
>>that it would require more memory at that time.)
>>
>>
>
>That doesn't follow either. I think you may have some bottleneck that
>causes client requests to pile up during a backup dump.
>
> regards, tom lane
>
>
Ok, that explains the number of arrays... max_connections / 16.
Thanks... my mind works better when I can associate actual settings to
effects like that. And I'm sure that performance takes a hit during out
back-up dump. We're in the process of migrating them to dedicated mirror
machine to run dumps/reports etc from crons so that it won't negatively
affect the DB servers that get queries from the web applications.
Thanks again for clarification.
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: dylists@ptd.net, tgl@sss.pgh.pa.us
Subject: Re: Tuning shared_buffers with ipcs ?
In-Reply-To: <41703E94.3030800@ptd.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