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

From: Mark Wong <markw(at)osdl(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-15 21:56:30
Message-ID: 20041015145630.A21918@osdl.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Oct 15, 2004 at 05:37:50PM -0400, 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?
>

Ah, yes. Ok. It's not being configured with any options. That'll be easy to
rememdy though. I'll get that change made and we can try again.

Mark

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Mark Wong 2004-10-15 22:10:22 Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...
Previous Message Tom Lane 2004-10-15 21:44:34 Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...