Re: performance bottlenecks on lock transactionid

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: 王若楠 <wrn(at)hljdx(dot)net>, pgsql-performance <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: performance bottlenecks on lock transactionid
Date: 2019-08-14 07:31:29
Message-ID: 0b8d46afd99b0eba5069031c9d88d6c9a2c10679.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

王若楠 wrote:
> We used benchmarksql 4.1.0 to test the performance of PG12 beta TPCC.
> We found performance bottlenecks on lock transactionid.

You included an attachment with results from the "pg_locks" view
where "granted" is FALSE for all entries.

I'll assume that these are not *all* the entries in the view, right?

Since the locks are waiting for different transaction IDs, I'd
assume that this is just a case of contention: many transactions are
trying to modify the same rows concurrently.

This is to be expected.
Perhaps your benchmark is running with too many connections on
too few table rows?

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message 王若楠 2019-08-14 07:57:04 re:Re: performance bottlenecks on lock transactionid
Previous Message Adrian Klaver 2019-08-13 17:57:05 Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg