Re: spinlocks on HP-UX

Tatsuo Ishii <ishii@postgresql.org>

From: Tatsuo Ishii <ishii@postgresql.org>

To: robertmhaas@gmail.com

Cc: pgsql-hackers@postgresql.org

Date: 2011-09-06T14:11:01Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Typo fixes.
- 0510b62d9115 9.2.0 cited

> That would be great.  What I've been using as a test case is pgbench
> -S -c $NUM_CPU_CORES -j $NUM_CPU_CORES with scale factor 100 and
> shared_buffers=8GB.
> 
> I think what you'd want to compare is the performance of unpatched
> master, vs. the performance with this line added to s_lock.h for your
> architecture:
> 
> #define TAS_SPIN(lock)  (*(lock) ? 1 : TAS(lock))
> 
> We've now added that line for ia64 (the line is present in two
> different places in the file, one for GCC and the other for HP's
> compiler).  So the question is whether we need it for any other
> architectures.

Ok. Let me talk to IBM guys...
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp