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

Re: User concurrency thresholding: where do I look?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Boreham <david_list(at)boreham(dot)org>
Cc: "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: User concurrency thresholding: where do I look?
Date: 2007-07-21 04:26:10
Message-ID: 20297.1184991970@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
David Boreham <david_list(at)boreham(dot)org> writes:
> Tom Lane wrote:
>> Having malloc/free use
>> an internal mutex is necessary in multi-threaded programs, but the
>> backend isn't multi-threaded.  

> Hmm...confused. I'm not following why then there is contention for the 
> mutex.

There isn't any contention for that mutex; Jignesh's results merely show
that it was taken and released a lot of times.

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Jozsef SzalayDate: 2007-07-22 15:29:04
Subject: Simple select hangs while CPU close to 100%
Previous:From: David BorehamDate: 2007-07-21 03:31:14
Subject: Re: User concurrency thresholding: where do I look?

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