Re: spinlock contention - Mailing list pgsql-hackers

From Robert Haas
Subject Re: spinlock contention
Date
Msg-id BANLkTik4wWzaWXcL-oamrKAZX1pGa9yvJQ@mail.gmail.com
Whole thread Raw
In response to Re: spinlock contention  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
On Tue, Jun 28, 2011 at 8:11 PM, Florian Pflug <fgp@phlo.org> wrote:
>> I wrote a little script to show to reorganize this data in a
>> possibly-easier-to-understand format - ordering each column from
>> lowest to highest, and showing each algorithm as a multiple of the
>> cheapest value for that column:
>
> If you're OK with that, I'd like to add that to the lockbench
> repo.

It's a piece of crap, but you're welcome to try to fix it up.  See attached.

With respect to the apparent lack of impact of the sleep loop, I can
only speculate that this test case doesn't really mimic real-world
conditions inside the backend very well.  There is a lot more going on
there - multiple locks, lots of memory access, etc.  But I don't
really understand it either.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade defaulting to port 25432
Next
From: Robert Haas
Date:
Subject: Re: time-delayed standbys