From 82e429794b348cd80c1d1b011e21ffac98bc6e88 Mon Sep 17 00:00:00 2001 From: Simon Riggs Date: Tue, 9 Oct 2012 08:15:23 +0100 Subject: Add microsecs/op display to pg_test_fsync utility e.g. fsync 2103.613 ops/sec ( 475 microsecs/op) Peter Geoghegan --- doc/src/sgml/pgtestfsync.sgml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/pgtestfsync.sgml b/doc/src/sgml/pgtestfsync.sgml index 95ba3b81e0c..00ef209fa25 100644 --- a/doc/src/sgml/pgtestfsync.sgml +++ b/doc/src/sgml/pgtestfsync.sgml @@ -30,11 +30,14 @@ pg_test_fsync is intended to give you a reasonable idea of what the fastest is on your specific system, - as well as supplying diagnostic information in the event of an - identified I/O problem. However, differences shown by pg_test_fsync - might not make any difference in real database throughput, especially - since many database servers are not speed-limited by their transaction - logs. + as well as supplying diagnostic information in the event of an identified I/O + problem. However, differences shown by + pg_test_fsync might not make any significant + difference in real database throughput, especially since many database servers + are not speed-limited by their transaction logs. + pg_test_fsync reports average file sync operation + time in microseconds for each wal_sync_method, which can be used to inform + efforts to optimize the value of commit_delay. -- cgit v1.2.3