Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
7db0dc0e
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,发现更多精彩内容 >>
提交
7db0dc0e
编写于
10月 06, 2013
作者:
N
Noah Misch
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
pgbench: Comment on thread timing hazards.
Reviewed by Fabien COELHO.
上级
bf261798
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
10 addition
and
1 deletion
+10
-1
contrib/pgbench/pgbench.c
contrib/pgbench/pgbench.c
+10
-1
未找到文件。
contrib/pgbench/pgbench.c
浏览文件 @
7db0dc0e
...
...
@@ -2896,7 +2896,16 @@ main(int argc, char **argv)
}
disconnect_all
(
state
,
nclients
);
/* get end time */
/*
* XXX We compute results as though every client of every thread started
* and finished at the same time. That model can diverge noticeably from
* reality for a short benchmark run involving relatively many threads.
* The first thread may process notably many transactions before the last
* thread begins. Improving the model alone would bring limited benefit,
* because performance during those periods of partial thread count can
* easily exceed steady state performance. This is one of the many ways
* short runs convey deceptive performance figures.
*/
INSTR_TIME_SET_CURRENT
(
total_time
);
INSTR_TIME_SUBTRACT
(
total_time
,
start_time
);
printResults
(
ttype
,
total_xacts
,
nclients
,
threads
,
nthreads
,
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录