From: Josh Berkus <josh@agliodbs.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: User concurrency thresholding: where do I look?
Date: Fri, 20 Jul 2007 10:17:35 -0700
Message-ID: <46A0EE2F.4080100@agliodbs.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0707201237070.2776@westnet.com>
References: <200707190828.59088.josh@agliodbs.com>
<20070719173704.GA12084@alvh.no-ip.org>
<14009.1184867115@sss.pgh.pa.us>
<200707191819.13899.josh@agliodbs.com>
<Pine.GSO.4.64.0707201237070.2776@westnet.com>
Greg,
> There's so much going on with a TPC-C kind of workload. Has anyone ever
> looked into quantifying scaling for more fundamental operations? There
> are so many places a complicated workload could get caught up that
> starting there is hard. I've found it's helpful to see the breaking
> points for simpler operations, then compare how things change as each
> new transaction element is introduced.
... eagerly awaiting Michael Doilson's PgUnitTest ....
--Josh
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: josh@agliodbs.com, gsmith@gregsmith.com
Subject: Re: User concurrency thresholding: where do I look?
In-Reply-To: <46A0EE2F.4080100@agliodbs.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