Re: shared_buffers/effective_cache_size on 96GB server - Mailing list pgsql-performance

From Shaun Thomas
Subject Re: shared_buffers/effective_cache_size on 96GB server
Date
Msg-id 5075BC09.8010006@optionshouse.com
Whole thread Raw
In response to Re: shared_buffers/effective_cache_size on 96GB server  (Claudio Freire <klaussfreire@gmail.com>)
Responses Re: shared_buffers/effective_cache_size on 96GB server  (Claudio Freire <klaussfreire@gmail.com>)
List pgsql-performance
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


pgsql-performance by date:

Previous
From: Claudio Freire
Date:
Subject: Re: Hyperthreading (was: Two identical systems, radically different performance)
Next
From: Claudio Freire
Date:
Subject: Re: shared_buffers/effective_cache_size on 96GB server