pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Need help with 8.4 Performance Testing
Date: Mon, 8 Dec 2008 17:52:30 -0500 (EST)
Message-ID: <Pine.GSO.4.64.0812081731510.26019@westnet.com> (raw)
In-Reply-To: <dcc563d10812081231y6c71601am677ba828ff0b515e@mail.gmail.com>
References: <200812071138.01215.josh@agliodbs.com>
	<dcc563d10812072140q1cb257cbs8140b390759cb1a5@mail.gmail.com>
	<Pine.GSO.4.64.0812081442410.5242@westnet.com>
	<dcc563d10812081231y6c71601am677ba828ff0b515e@mail.gmail.com>

On Mon, 8 Dec 2008, Scott Marlowe wrote:

> Well, I have 32 Gig of ram and wanted to test it against a database
> that was at least twice as big as memory.  I'm not sure why you'd
> consider the results uninteresting though, I'd think knowing how the
> db will perform with a very large transactional store that is twice or
> more the size of memory would be when it starts getting interesting.

If you refer back to the picture associated with the link Josh suggested:

http://www.westnet.com/~gsmith/gregsmith/content/postgresql/scaling.png

You'll see that pgbench results hit a big drop once you clear the amount 
of memory being used to cache the accounts table.  This curve isn't unique 
to what I did; I've seen the same basic shape traced out by multiple other 
testers on different hardware, independent of me.  It just expands to the 
right based on the amount of RAM available.

All I was trying to suggest was that even if you've got 32GB of RAM, you 
may already be into the more flat right section of that curve even with a 
40GB database.  That was a little system with 1GB of RAM+256MB of disk 
cache, and it was already toast at 750MB of database.  Once you've gotten 
a database big enough to reach that point, results degrade to something 
related to database seeks/second rather than anything else, and further 
increases don't give you that much more info.  This is why I'm not sure if 
the current limit really matters with 32GB of RAM, but it sure will be 
important if you want any sort of useful pgbench results at 64GB.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD



view thread (56+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0812081731510.26019@westnet.com>
Permalink:  ../Pine.GSO.4.64.0812081731510.26019@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0812081731510.26019@westnet.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: gsmith@gregsmith.com, scott.marlowe@gmail.com, josh@agliodbs.com
  Subject: Re: Need help with 8.4 Performance Testing
  In-Reply-To: <Pine.GSO.4.64.0812081731510.26019@westnet.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