pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Rod Taylor <pg@rbt.ca>
Cc: Christopher Browne <cbbrowne@acm.org>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Working on huge RAM based datasets
Date: Mon, 12 Jul 2004 14:01:10 -0400
Message-ID: <40F2D1E6.10504@Yahoo.com> (raw)
In-Reply-To: <200407120938.01764.josh@agliodbs.com>
References: <6EE64EF3AB31D5448D0007DD34EEB34101AEC2@Herge.rcsinc.local>
	<m3r7rio4pf.fsf@wolfe.cbbrowne.com>
	<1089643087.42256.7.camel@jester>
	<200407120938.01764.josh@agliodbs.com>

On 7/12/2004 12:38 PM, Josh Berkus wrote:

> Rond, Chris,
> 
>> > What would be most interesting to see is whether this makes it wise to
>> > increase shared buffer size.  It may be more effective to bump down
>> > the cache a little, and bump up sort memory; hard to tell.
>>
>> How do we go about scheduling tests with the OSDL folks? If they could
>> do 10 runs with buffers between 1k and 500k it would help us get a broad
>> view of the situation.
> 
> Yes.   We'll need to.   However, I'd like to wait until we're officially in 
> Beta.   I'll be seeing the OSDL folks in person (PostgreSQL+OSDL BOF at Linux 
> World Expo!!)  in a couple of weeks.
> 

Don't forget to add that ARC needs some time actually to let the 
algorithm adjust the queue sizes and populate the cache according to the 
access pattern. You can't start a virgin postmaster and then slam on the 
accellerator of your test application by launching 500 concurrent 
clients out of the blue and expect that it starts off airborne.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




view thread (16+ messages)  latest in thread

Message-ID: <40F2D1E6.10504@Yahoo.com>
Permalink:  ../40F2D1E6.10504@Yahoo.com/
Also on:    postgresql.org/message-id/40F2D1E6.10504@Yahoo.com

 · 

reply

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: JanWieck@Yahoo.com, josh@agliodbs.com, pg@rbt.ca, cbbrowne@acm.org
  Subject: Re: Working on huge RAM based datasets
  In-Reply-To: <40F2D1E6.10504@Yahoo.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