Re: CLOG contention, part 2
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Janes <jeff.janes@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-02-28T19:21:41Z
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 →
-
Call check_keywords.pl in maintainer-check
- 9bf8603c7a91 9.2.0 cited
-
Make the number of CLOG buffers adaptive, based on shared_buffers.
- 33aaa139e630 9.2.0 cited
On Tue, Feb 28, 2012 at 6:11 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Mon, Feb 27, 2012 at 4:03 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> So please use a scale factor that the hardware can cope with. > > OK. I tested this out on Nate Boley's 32-core AMD machine, using > scale factor 100 and scale factor 300. I initialized it with Simon's > patch, which should have the effect of rendering the entire table > unhinted and giving each row a different XID. Thanks for making the test. I think this tells me the only real way to do this kind of testing is not at arms length from a test machine. So time to get my hands on a machine, but not for this release. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services