Re: testing ProcArrayLock patches

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

To: "Robert Haas" <robertmhaas@gmail.com>, <pgsql-hackers@postgresql.org>, "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

Date: 2011-11-18T17:20:07Z

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 →

Don't elide blank lines when accumulating psql command history.
- ff4fd4bf53c5 9.2.0 cited

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote:

> We have a 32-core Intel box (4 x X7560 @ 2.27GHz) with 256 GB
> RAM.

In case anyone cares, this is the same box for which I posted STREAM
test results a while back.  The PostgreSQL tests seem to peak on
this 32-core box at 64 clients, while the STREAM test of raw RAM
speed kept increasing up to 128 clients.  Overall, though, it's
impressive how close PostgreSQL is now coming to the raw RAM access
speed curve.

http://archives.postgresql.org/pgsql-hackers/2011-08/msg01306.php

-Kevin