From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: User concurrency thresholding: where do I look?
Date: Tue, 31 Jul 2007 14:33:20 -0700
Message-ID: <200707311433.20568.josh@agliodbs.com> (raw)
In-Reply-To: <1185527727.4191.22.camel@ebony.site>
References: <200707190828.59088.josh@agliodbs.com>
<46A90F83.8050401@sun.com>
<1185527727.4191.22.camel@ebony.site>
Simon,
> Well thats pretty weird. That code path clearly only happens once per
> transaction and ought to be fast. The other code paths that take
> ProcArrayLock like TransactionIdIsInProgress() and GetSnapshotData()
> ought to spend more time holding the lock. Presumably you are running
> with a fair number of SERIALIZABLE transactions?
Given that this is TPCC-analog, I'd assume that we are.
Jignesh?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
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
Subject: Re: User concurrency thresholding: where do I look?
In-Reply-To: <200707311433.20568.josh@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