Horton

Re: 16-bit page checksums for 9.2

David Fetter <david@fetter.org>

View thread
From: David Fetter <david@fetter.org>
To: Peter Geoghegan <peter@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org, Noah Misch <noah@leadboat.com>, Simon Riggs <simon@2ndquadrant.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Andres Freund <andres@anarazel.de>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, aidan@highrise.ca, stark@mit.edu, Robert Haas <robertmhaas@gmail.com>
Date: 2012-02-22T23:51:00Z
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. Wakeup WALWriter as needed for asynchronous commit performance.

On Wed, Feb 22, 2012 at 11:17:53PM +0000, Peter Geoghegan wrote:
> I decided that it would be worth benchmarking this patch.
> Specifically, I tested:
> 
> master, as a basis of comparison
> 
> checksum16_with_wallogged_hint_bits.v10.patch, page_checksums = 'on'
> 
> checksum16_with_wallogged_hint_bits.v10.patch, page_checksums = 'off'
> 
> This test was performed using pgbench-tools. At different client
> counts and scaling factors "1,10,100", performance of an update.sql
> workload was tested.

Looks interesting.  Could you get some error bars around the numbers
plotted, and possibly some scaling factors between 10 and 100?

For the former, I'm looking for whether those changes are within
ordinary variation, and in the latter, some better idea of what the
curve looks like.

Cheers,
David.
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate