Skip site navigation (1) Skip section navigation (2)

Re: spinlock->pthread_mutex : real world results

From: Nils Goroll <slink(at)schokola(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: spinlock->pthread_mutex : real world results
Date: 2012-08-06 22:10:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

> 1. How much we're paying for this in the uncontended case?

Using glibc, we have the overhead of an additional library function call, which 
we could eliminate by pulling in the code from glibc/nptl or a source of other 
proven reference code.

The pgbench results I had posted before could give an 
indication on the higher base cost for the simple approach.

I have mentioned this before: While I agree that minimizing the base overhead is 
good, IMHO, optimizing the worst case is the important part here.


In response to

pgsql-hackers by date

Next:From: Amit KapilaDate: 2012-08-07 03:07:29
Subject: Re: WIP patch for LATERAL subqueries
Previous:From: Martijn van OosterhoutDate: 2012-08-06 21:25:20
Subject: Re: spinlock->pthread_mutex : real world results

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group