Re: LWLock contention: I think I understand the problem - Mailing list pgsql-hackers

From Jeffrey W. Baker
Subject Re: LWLock contention: I think I understand the problem
Date
Msg-id Pine.LNX.4.33.0201032057460.26288-100000@windmill.gghcwest.com
Whole thread Raw
In response to Re: LWLock contention: I think I understand the problem  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers

On Thu, 3 Jan 2002, Bruce Momjian wrote:

> Tom Lane wrote:
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > OK, so now we know that while the new lock code handles the select(1)
> > > problem better, we also know that on AIX the old select(1) code wasn't
> > > as bad as we thought.
> >
> > It still seems that the select() blocking method should be a loser.
>
> No question the new locking code is better.  It just frustrates me we
> can't get something to show that.

Even though I haven't completed controlled benchmarks yet, 7.2b4 was using
all of my CPU time, whereas a patched version is using around half of CPU
time, all in user space.

I think not pissing away all our time in the scheduler is a big
improvement!

-jwb



pgsql-hackers by date:

Previous
From: "Rod Taylor"
Date:
Subject: Re: Some interesting results from tweaking spinlocks
Next
From: Kaare Rasmussen
Date:
Subject: Re: Updated TODO item