Re: mmap (was First set of OSDL Shared Mem scalability results, some wierdness ...

From: Mark Wong <markw(at)osdl(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sean Chittenden <sean(at)chittenden(dot)org>, Kevin Brown <kevin(at)sysexperts(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: mmap (was First set of OSDL Shared Mem scalability results, some wierdness ...
Date: 2004-10-18 15:28:10
Message-ID: 20041018082810.A11062@osdl.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Oct 15, 2004 at 09:22:03PM -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Mark Wong <markw(at)osdl(dot)org> writes:
> > > I know where the do_sigaction is coming from in this particular case.
> > > Manfred Spraul tracked it to a pair of pgsignal calls in libpq.
> > > Commenting out those two calls out virtually eliminates do_sigaction from
> > > the kernel profile for this workload.
> >
> > Hmm, I suppose those are the ones associated with suppressing SIGPIPE
> > during send(). It looks to me like those should go away in 8.0 if you
> > have compiled with ENABLE_THREAD_SAFETY ... exactly how is PG being
> > built in the current round of tests?
>
> Yes, those calls are gone in 8.0 with --enable-thread-safety and were
> added specifically because of Manfred's reports.
>

Ok, I had the build commands changed for installing PostgreSQL in STP.
The do_sigaction call isn't at the top of the profile anymore, here's
a reference for those who are interested; it should have the same test
parameters as the one Tom referenced a little earlier:
http://khack.osdl.org/stp/298230/

Mark

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Rod Dutton 2004-10-18 18:01:25 Queries slow using stored procedures
Previous Message charavay 2004-10-18 08:50:21 Indexes performance