From: Stephen Frost <sfrost@snowman.net>
To: Dan Harris <fbsd@drivefaster.net>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: large dataset with write vs read clients
Date: Thu, 7 Oct 2010 14:57:48 -0400
Message-ID: <20101007185748.GZ26232@tamriel.snowman.net> (raw)
In-Reply-To: <4CAE1192.5080807@drivefaster.net>
References: <AANLkTimNJc=0ffgRO_gO6Vsq06=aqBYXZouhbv0kBe-i@mail.gmail.com>
<4CAE1192.5080807@drivefaster.net>
* Dan Harris (fbsd@drivefaster.net) wrote:
> On 10/7/10 11:47 AM, Aaron Turner wrote:
>> Basically, each connection is taking about 100MB resident. As we need
>> to increase the number of threads to be able to query all the devices
>> in the 5 minute window, we're running out of memory.
> I think the first thing to do is look into using a connection pooler
> like pgpool to reduce your connection memory overhead.
Yeah.. Having the number of database connections be close to the number
of processors is usually recommended.
Stephen
Attachments:
signature.asc (application/pgp-signature, 196B) download
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: sfrost@snowman.net, fbsd@drivefaster.net
Subject: Re: large dataset with write vs read clients
In-Reply-To: <20101007185748.GZ26232@tamriel.snowman.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