Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... - Mailing list pgsql-performance

From Tom Lane
Subject Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...
Date
Msg-id 26451.1097875649@sss.pgh.pa.us
Whole thread Raw
In response to Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...  (Josh Berkus <josh@agliodbs.com>)
Responses Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...
List pgsql-performance
Josh Berkus <josh@agliodbs.com> writes:
>> I suspect the reason recalc_sigpending_tsk is so high is that the
>> original coding of PG_TRY involved saving and restoring the signal mask,
>> which led to a whole lot of sigsetmask-type kernel calls.  Is this test
>> with beta3, or something older?

> Beta3, *without* Gavin or Neil's Futex patch.

Hmm, in that case the cost deserves some further investigation.  Can we
find out just what that routine does and where it's being called from?

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: mmap (was First set of OSDL Shared Mem scalability results, some wierdness ...
Next
From: Mark Wong
Date:
Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...