From: Scott Marlowe <scott.marlowe@gmail.com>
To: Greg Smith <gsmith@gregsmith.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 13:31:29 -0700
Message-ID: <dcc563d10812081231y6c71601am677ba828ff0b515e@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0812081442410.5242@westnet.com>
References: <200812071138.01215.josh@agliodbs.com>
<dcc563d10812072140q1cb257cbs8140b390759cb1a5@mail.gmail.com>
<Pine.GSO.4.64.0812081442410.5242@westnet.com>
On Mon, Dec 8, 2008 at 1:15 PM, Greg Smith <gsmith@gregsmith.com> wrote:
> On Sun, 7 Dec 2008, Scott Marlowe wrote:
>
>> When I last used pgbench I wanted to test it with an extremely large
>> dataset, but it maxes out at -s 4xxx or so, and that's only in the
>> 40Gigabyte range. Is the limit raised for the pgbench included in
>> contrib in 8.4? I'm guessing it's an arbitrary limit.
>
> There's no artificial limit, just ones that result from things like integer
> overflow. I don't think has been an issue so far because pgbench becomes
> seek limited and stops producing interesting results once the database
> exceeds the sum of all available caching, which means you'd need more than
> 32GB of RAM in the system running pgbench before this is an issue. Which
> happens to be the largest size system I've ever ran it on...
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.
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: scott.marlowe@gmail.com, gsmith@gregsmith.com, josh@agliodbs.com
Subject: Re: Need help with 8.4 Performance Testing
In-Reply-To: <dcc563d10812081231y6c71601am677ba828ff0b515e@mail.gmail.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