Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
82e42979
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
82e42979
编写于
10月 09, 2012
作者:
S
Simon Riggs
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add microsecs/op display to pg_test_fsync utility
e.g. fsync 2103.613 ops/sec ( 475 microsecs/op) Peter Geoghegan
上级
bc433317
变更
2
显示空白变更内容
内联
并排
Showing
2 changed file
with
12 addition
and
7 deletion
+12
-7
contrib/pg_test_fsync/pg_test_fsync.c
contrib/pg_test_fsync/pg_test_fsync.c
+4
-2
doc/src/sgml/pgtestfsync.sgml
doc/src/sgml/pgtestfsync.sgml
+8
-5
未找到文件。
contrib/pg_test_fsync/pg_test_fsync.c
浏览文件 @
82e42979
...
...
@@ -25,7 +25,8 @@
#define LABEL_FORMAT " %-32s"
#define NA_FORMAT "%18s"
#define OPS_FORMAT "%9.3f ops/sec"
#define OPS_FORMAT "%9.3f ops/sec (%6.f microsecs/op)"
#define USECS_SEC 1000000
/* These are macros to avoid timing the function call overhead. */
#ifndef WIN32
...
...
@@ -568,8 +569,9 @@ print_elapse(struct timeval start_t, struct timeval stop_t, int ops)
double
total_time
=
(
stop_t
.
tv_sec
-
start_t
.
tv_sec
)
+
(
stop_t
.
tv_usec
-
start_t
.
tv_usec
)
*
0
.
000001
;
double
per_second
=
ops
/
total_time
;
double
avg_op_time_us
=
(
total_time
/
ops
)
*
USECS_SEC
;
printf
(
OPS_FORMAT
"
\n
"
,
per_second
);
printf
(
OPS_FORMAT
"
\n
"
,
per_second
,
avg_op_time_us
);
}
#ifndef WIN32
...
...
doc/src/sgml/pgtestfsync.sgml
浏览文件 @
82e42979
...
...
@@ -30,11 +30,14 @@
<application>pg_test_fsync</> is intended to give you a reasonable
idea of what the fastest <xref linkend="guc-wal-sync-method"> is on your
specific system,
as well as supplying diagnostic information in the event of an
identified I/O problem. However, differences shown by <application>pg_test_fsync</application>
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
<application>pg_test_fsync</application> might not make any significant
difference in real database throughput, especially since many database servers
are not speed-limited by their transaction logs.
<application>pg_test_fsync</application> 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 <varname>commit_delay</varname>.
</para>
</refsect1>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录