Horton
Menu

Re: Doc patch making firm recommendation for setting the value of commit_delay

Noah Misch <noah@leadboat.com>

View thread
From: Noah Misch <noah@leadboat.com>
To: Peter Geoghegan <peter@2ndquadrant.com>
Cc: PG Hackers <pgsql-hackers@postgresql.org>
Date: 2013-01-21T13:10:33Z
Lists: pgsql-hackers 
On Mon, Jan 21, 2013 at 12:23:21AM +0000, Peter Geoghegan wrote:
> On 19 January 2013 20:38, Noah Misch <noah@leadboat.com> wrote:
> > staticloud.com seems to be gone.  Would you repost these?
> 
> I've pushed these to a git repo, hosted on github.
> 
> https://github.com/petergeoghegan/commit_delay_benchmarks
> 
> I'm sorry that I didn't take the time to make the html benchmarks
> easily viewable within a browser on this occasion.

That's plenty convenient; thanks.

What filesystem did you use for testing?  Would you also provide /proc/cpuinfo
or a rough description of the system's CPUs?

Commits

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

  1. Add microsecs/op display to pg_test_fsync utility