From: Shaun Thomas <sthomas@optionshouse.com>
To: Claudio Freire <klaussfreire@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Julien Cigar <jcigar@ulb.ac.be>
Cc: pgsql-performance@postgresql.org
Subject: Re: shared_buffers/effective_cache_size on 96GB server
Date: Wed, 10 Oct 2012 13:18:49 -0500
Message-ID: <5075BC09.8010006@optionshouse.com> (raw)
In-Reply-To: <CAGTBQpZ0E2xyAeNZy6a4uyhzyfhSNMv3TRDeLWdeT16RYYMPOg@mail.gmail.com>
References: <CADKbJJUTr9ZWkbajR-7_6qaAsWH0=09=2AMo67C_Az-raKZE4w@mail.gmail.com>
<50752DB2.6060004@ulb.ac.be>
<20121010161012.GE11892@momjian.us>
<CAGTBQpZ0E2xyAeNZy6a4uyhzyfhSNMv3TRDeLWdeT16RYYMPOg@mail.gmail.com>
On 10/10/2012 12:05 PM, Claudio Freire wrote:
> Why does nobody every mention that concurrent access has to be taken
> into account?
That's actually a good point. But if you have one giant database, the
overlap of which tables are being accessed by various sessions is going
to be immense.
There probably should be a point about this in the docs, though. There
are more and more shared-hosting setups or places that spread their data
horizontally across separate databases for various clients, and in those
cases, parallel usage does not imply overlap.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
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: sthomas@optionshouse.com, klaussfreire@gmail.com, bruce@momjian.us, jcigar@ulb.ac.be
Subject: Re: shared_buffers/effective_cache_size on 96GB server
In-Reply-To: <5075BC09.8010006@optionshouse.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