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

From Bruce Momjian
Subject Re: LWLock contention: I think I understand the problem
Date
Msg-id 200201040502.g0452TW23333@candle.pha.pa.us
Whole thread Raw
In response to LWLock contention: I think I understand the problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > > 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!

Yes, the new patch is clearly better than 7.2b4.  We are really hoping
to see the patched version beat 7.1.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: LWLock contention: I think I understand the problem
Next
From: Bruce Momjian
Date:
Subject: Re: More problem with scripts