On Fri, Mar 15, 2013 at 05:47:30PM -0400, Tom Lane wrote:
Noah Misch n...@leadboat.com writes:
I'm marking this patch Ready for Committer, qualified with a recommendation
to
adopt only the wal.sgml changes.
I've committed this along with some further wordsmithing. I kept
Peter's
Noah Misch n...@leadboat.com writes:
I'm marking this patch Ready for Committer, qualified with a recommendation to
adopt only the wal.sgml changes.
I've committed this along with some further wordsmithing. I kept
Peter's change to pg_test_fsync's default -s value; I've always felt
that 2
On Mon, Jan 28, 2013 at 04:48:56AM +, Peter Geoghegan wrote:
On 28 January 2013 03:34, Noah Misch n...@leadboat.com wrote:
Would you commit to the same git repository the pgbench-tools data for the
graphs appearing in that blog post? I couldn't readily tell what was
happening below 16
On Mon, Jan 28, 2013 at 04:29:12AM +, Peter Geoghegan wrote:
On 28 January 2013 03:34, Noah Misch n...@leadboat.com wrote:
On the EBS configuration with volatile fsync timings, the variability didn't
go away with 15s runs. On systems with stable fsync times, 15s was no
better
than
Hi Noah,
On 27 January 2013 02:31, Noah Misch n...@leadboat.com wrote:
I did a few more benchmarks along the spectrum.
So that's a nice 27-53% improvement, fairly similar to the pattern for your
laptop pgbench numbers.
I presume that this applies to a tpc-b benchmark (the pgbench
default).
On Mon, Jan 28, 2013 at 12:16:24AM +, Peter Geoghegan wrote:
On 27 January 2013 02:31, Noah Misch n...@leadboat.com wrote:
I did a few more benchmarks along the spectrum.
So that's a nice 27-53% improvement, fairly similar to the pattern for your
laptop pgbench numbers.
I presume
On 28 January 2013 03:34, Noah Misch n...@leadboat.com wrote:
On the EBS configuration with volatile fsync timings, the variability didn't
go away with 15s runs. On systems with stable fsync times, 15s was no better
than 2s. Absent some particular reason to believe 5s is better than 2s, I
On 28 January 2013 03:34, Noah Misch n...@leadboat.com wrote:
Would you commit to the same git repository the pgbench-tools data for the
graphs appearing in that blog post? I couldn't readily tell what was
happening below 16 clients due to the graphed data points blending together.
I'm afraid
Hi Peter,
I took a look at this patch and the benchmarks you've furnished:
https://github.com/petergeoghegan/commit_delay_benchmarks
http://pgeoghegan.blogspot.com/2012/06/towards-14000-write-transactions-on-my.html
On Wed, Nov 14, 2012 at 08:44:26PM +, Peter Geoghegan wrote:
Attached is
On Mon, Jan 21, 2013 at 12:23:21AM +, Peter Geoghegan wrote:
On 19 January 2013 20:38, Noah Misch n...@leadboat.com wrote:
staticloud.com seems to be gone. Would you repost these?
I've pushed these to a git repo, hosted on github.
On Wed, Nov 14, 2012 at 08:44:26PM +, Peter Geoghegan wrote:
http://commit-delay-results-ssd-insert.staticloud.com
http://commit-delay-stripe-insert.staticloud.com
http://commit-delay-results-stripe-tpcb.staticloud.com
11 matches
Mail list logo