Horton

Re: spinlocks on powerpc

Manabu Ori <manabu.ori@gmail.com>

View thread
From: Manabu Ori <manabu.ori@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Tatsuo Ishii <ishii@postgresql.org>, robertmhaas@gmail.com, pgsql-hackers@postgresql.org
Date: 2012-01-02T17:10:31Z
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 →

  1. Use LWSYNC in place of SYNC/ISYNC in PPC spinlocks, where possible.

  2. Reduce sinval synchronization overhead.

Attachments

By the way...

2012/1/2 Tom Lane <tgl@sss.pgh.pa.us>
> (It's depressing that these numbers have hardly moved since August ---
> at least on this test, the work that Robert's done has not made any
> difference.)

I merged some results and created another graph.
Please find an attached png file and you'll see obvious
performance improvement...

All the results are run on the same system:
  Power 750 (32 physical cores, virtually 128 cores using SMT4)
  mem: 256GB
  OS: RHEL6.1 kernel 2.6.32-131.0.15.el6.ppc64
  gcc version 4.4.5 20110214 (Red Hat 4.4.5-6)