Re: Need to tune for Heavy Write - Mailing list pgsql-performance

From Jim Nasby
Subject Re: Need to tune for Heavy Write
Date
Msg-id 51AF6021-45B8-4C81-8B24-375837310342@nasby.net
Whole thread Raw
In response to Re: Need to tune for Heavy Write  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-performance
On Aug 4, 2011, at 10:07 AM, Scott Marlowe wrote:
> On Thu, Aug 4, 2011 at 7:57 AM, Kevin Grittner
> <Kevin.Grittner@wicourts.gov> wrote:
>>> RAM : 16 GB
>>
>>> effective_cache_size = 4096MB
>>
>> That should probably be more like 12GB to 15GB.  It probably won't
>> affect the load time here, but could affect other queries.
>
> Actually on a heavily written database a  large effective cache size
> makes things slower.

effective_cache_size or shared_buffers? I can see why a large shared_buffers could cause problems, but what effect does
effective_cache_sizehave on a write workload? 
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net



pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: DBT-5 & Postgres 9.0.3
Next
From: Greg Smith
Date:
Subject: Re: Raid 5 vs Raid 10 Benchmarks Using bonnie++