drbd mysql性能_drbd性能测试及调优
主库:
----total-cpu-usage---- -dsk/total- -net/total- ---paging-- ---system--
usr sys idl wai hiq siq| read writ| recv send| in out | int csw
5 4 41 51 0 0| 80k 19M| 959k 9388k| 0 0 |5697 13k
4 5 44 47 0 1| 88k 15M| 963k 9474k| 0 0 |4845 10k
7 4 36 53 0 0| 0 16M| 326k 9048k| 0 0 |5324 12k
8 3 41 47 0 1| 0 18M| 939k 8708k| 0 0 |5963 12k
7 4 30 59 0 0| 0 21M| 975k 9659k| 0 0 |5763 14k
...
6 5 42 48 0 0| 0 17M|1389k 7702k| 0 0 |5524 13k
10 3 39 48 0 0| 0 17M| 380k 10M| 0 0 |5198 11k
4 3 45 48 0 1| 0 19M| 950k 8993k| 0 0 |6003 14k
5 4 43 48 0 0| 0 13M| 991k 10M| 0 0 |4863 11k
--备库:
----total-cpu-usage---- -dsk/total- -net/total- ---paging-- ---system--
usr sys idl wai hiq siq| read writ| recv send| in out | int csw
9 5 86 0 0 1| 0 8580k|9114k 319k| 0 0 | 12k 14k
4 3 92 0 0 1| 0 7572k|7992k 280k| 0 0 |9422 12k
0 3 96 0 0 1| 0 8348k|8842k 309k| 0 0 | 10k 14k
0 2 97 0 0 1| 0 7544k|7988k 279k| 0 0 |9351 12k
0 3 96 0 0 1| 0 9164k| 10M 345k| 0 0 | 12k 14k
0 3 97 0 0 1| 0 8180k|8232k 293k| 0 0 |9662 13k
...
0 3 97 0 0 1| 0 8544k|9036k 314k| 0 0 | 10k 14k
0 3 96 0 0 1| 0 7672k|8123k 285k| 0 0 |9543 12k
0 3 97 0 0 1| 0 8888k|9448k 327k| 0 0 | 11k 14k^C
可以看出,主库每秒要写10几兆左右,网络发送也要将近10M,从库写每秒7M-9M左右,网络接收也和写操作的速率差不多
查看下sysbench的测试表的大小:
[[email protected] mcldb]# du -sh sbtest.*
12Ksbtest.frm
1.2Gsbtest.ibd
2.测试drbd集群状态的性能:
采用复合模式,即增删改查模式:
[[email protected] ~]# sysbench --oltp-auto-inc=off --max-requests=0 --max-time=60 --num-threads=4 --test=oltp --db-driver=mysql --mysql-host=192.168.1.163 --mysql-port=3306 --mysql-user=root --mysql-password=123456 --mysql-db=mcldb --oltp-test-mode=complex run
sysbench 0.4.10: multi-threaded system evaluation benchmark
WARNING: Preparing of "BEGIN" is unsupported, using emulation
(last message repeated 3 times)
Running the test with following options:
Number of threads: 4
Doing OLTP test.
Running mixed OLTP test
Using Special distribution (12 iterations, 1 pct of values are returned in 75 pct cases)
Using "BEGIN" for starting transactions
Not using auto_inc on the id column
Threads started!
Time limit exceeded, exiting...
(last message repeated 3 times)
Done.
OLTP test statistics:
queries performed:
read: 11130
write: 3975
other: 1590
total: 16695
transactions: 795 (13.21 per sec.)
deadlocks: 0 (0.00 per sec.)
read/write requests: 15105 (251.06 per sec.)
other operations: 1590 (26.43 per sec.)
Test execution summary:
total time: 60.1639s
total number of events: 795
total time taken by event execution: 240.4650
per-request statistics:
min: 100.55ms
avg: 302.47ms
max: 889.42ms
approx. 95 percentile: 614.07ms
Threads fairness:
events (avg/stddev): 198.7500/3.90
execution time (avg/stddev): 60.1163/0.03
可以看出,1分钟内请求了16695次查询,tps为13.21(不足为奇,我的机子就比较烂)
3.测试单机状态的性能:
把备库离线:
crm(live)# status
Last updated: Mon Jul 28 18:23:32 2014
Last change: Sat Jul 26 10:05:58 2014 via cibadmin on db163
Stack: classic openais (with plugin)
Current DC: db163 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726
2 Nodes configured, 2 expected votes
7 Resources configured
Online: [ db162 db163 ]
Master/Slave Set: ms_drbd_mysql [drbd_mysql]
Masters: [ db163 ]
Slaves: [ db162 ]
Resource Group: g_mysql
fs_mysql(ocf::heartbeat:Filesystem):Started db163
p_ip_mysql(ocf::heartbeat:IPaddr2):Started db163
mysqld(lsb:mysqld):Started db163
Clone Set: cl_ping [p_ping]
Started: [ db162 db163 ]
crm(live)# node standby db162
再来看下主库drbd的状态:
[[email protected] mcldb]# cat /proc/drbd
version: 8.4.4 (api:1/proto:86-101)
GIT-hash: 599f286440bd633d15d5ff985204aff4bccffadd build by [email protected], 2013-10-14 15:33:06
0: cs:WFConnection ro:Primary/ Unknownds:UpToDate/ DUnknownC r-----
ns:6074648 nr:0 dw:6075004 dr:294960 al:466 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:308
确实已经不在同步数据了,下面再来测试:
[[email protected] ~]# sysbench --oltp-auto-inc=off --max-requests=0 --max-time=60 --num-threads=4 --test=oltp --db-driver=mysql --mysql-host=192.168.1.163 --mysql-port=3306 --mysql-user=root --mysql-password=123456 --mysql-db=mcldb --oltp-test-mode=complex run
sysbench 0.4.10: multi-threaded system evaluation benchmark
WARNING: Preparing of "BEGIN" is unsupported, using emulation
(last message repeated 3 times)
Running the test with following options:
Number of threads: 4
Doing OLTP test.
Running mixed OLTP test
Using Special distribution (12 iterations, 1 pct of values are returned in 75 pct cases)
Using "BEGIN" for starting transactions
Not using auto_inc on the id column
Threads started!
Time limit exceeded, exiting...
(last message repeated 3 times)
Done.
OLTP test statistics:
queries performed:
read: 16394
write: 5851
other: 2340
total: 24585
transactions: 1169 (19.45 per sec.)
deadlocks: 2 (0.03 per sec.)
read/write requests: 22245 (370.14 per sec.)
other operations: 2340 (38.94 per sec.)
Test execution summary:
total time: 60.0990s
total number of events: 1169
total time taken by event execution: 240.2136
per-request statistics:
min: 73.11ms
avg: 205.49ms
max: 741.33ms
approx. 95 percentile: 432.89ms
Threads fairness:
events (avg/stddev): 292.2500/3.34
execution time (avg/stddev): 60.0534/0.03确实有drbd的话,性能损耗了(1-16695/24585)= 32%,但目前drbd没有调优,下面调整下drbd的参数,再来测试
4.调优drbd后测试性能:
先还原drbd备库:
crm(live)# node online db162
crm(live)# status
Last updated: Mon Jul 28 18:45:16 2014
Last change: Mon Jul 28 18:45:30 2014 via crm_attribute on db162
Stack: classic openais (with plugin)
Current DC: db163 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726
2 Nodes configured, 2 expected votes
7 Resources configured
Online: [ db162 db163 ]
Master/Slave Set: ms_drbd_mysql [drbd_mysql]
Masters: [ db163 ]
Slaves: [ db162 ]
Resource Group: g_mysql
fs_mysql(ocf::heartbeat:Filesystem):Started db163
p_ip_mysql(ocf::heartbeat:IPaddr2):Started db163
mysqld(lsb:mysqld):Started db163
Clone Set: cl_ping [p_ping]
Started: [ db162 db163 ]
[[email protected] ~]# cat /proc/drbd
version: 8.4.4 (api:1/proto:86-101)
GIT-hash: 599f286440bd633d15d5ff985204aff4bccffadd build by [email protected], 2013-10-14 15:33:06
0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate C r-----
ns:0 nr:38064 dw:38064 dr:0 al:0 bm:18 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
可以看出,drbd又还原回来了,现在又开始了数据同步。
调整优化drbd参数:
[[email protected] ~]# vim /etc/drbd.d/global_common.conf
disk {
on-io-error detach;
disk-flushes no;
}
net {
max-buffers 8000; #增大缓存区为8000
max-epoch-size 8000;
sndbuf-size 0; #是sendbuffer自动调整
}
syncer {
rate 10M; #我的是百兆带宽,所以调整10M就行了
al-extents 257; #增大活动日志区为257个
}
common {
protocol C; #协议仍采用C,即主要把数据发送到从的tcp缓存区才算完成,这是最安全严格的方式了。
}
把文件也拷贝到从上面:
[[email protected] ~]# scp /etc/drbd.d/global_common.conf db162:/etc/drbd.d/
global_common.conf 100% 2181 2.1KB/s 00:00
主备都在线调整下配置文件:
[[email protected] ~]# drbdadm adjust all
[[email protected] ~]# drbdadm adjust all
再来测试:
[[email protected] ~]# sysbench --oltp-auto-inc=off --max-requests=0 --max-time=60 --num-threads=4 --test=oltp --db-driver=mysql --mysql-host=192.168.1.163 --mysql-port=3306 --mysql-user=root --mysql-password=123456 --mysql-db=mcldb --oltp-test-mode=complex run
sysbench 0.4.10: multi-threaded system evaluation benchmark
WARNING: Preparing of "BEGIN" is unsupported, using emulation
(last message repeated 3 times)
Running the test with following options:
Number of threads: 4
Doing OLTP test.
Running mixed OLTP test
Using Special distribution (12 iterations, 1 pct of values are returned in 75 pct cases)
Using "BEGIN" for starting transactions
Not using auto_inc on the id column
Threads started!
Time limit exceeded, exiting...
(last message repeated 3 times)
Done.
OLTP test statistics:
queries performed:
read: 16366
write: 5845
other: 2338
total: 24549
transactions: 1169 (19.45 per sec.)
deadlocks: 0 (0.00 per sec.)
read/write requests: 22211 (369.46 per sec.)
other operations: 2338 (38.89 per sec.)
Test execution summary:
total time: 60.1174s
total number of events: 1169
total time taken by event execution: 240.1222
per-request statistics:
min: 70.51ms
avg: 205.41ms
max: 685.97ms
approx. 95 percentile: 413.63ms
Threads fairness:
events (avg/stddev): 292.2500/5.45
execution time (avg/stddev): 60.0306/0.05
drbd mysql性能_drbd性能测试及调优相关推荐
- 基于Fabric的性能测试与调优实践
1 Fabric 性能测试现状 通俗的来讲,区块链是一种按照时间顺序将数据区块以顺序相连的方式组合成的一种链式数据结构,并以密码学方式保证的不可篡改和不可伪造的分布式账本.比特币(Bitcoin). ...
- 编写一个能监控到windows进程占用内存大小的脚本_Java性能监控分析及调优工具...
>>>推荐阅读<<< 1.性能测试学习笔记-场景设计 2.性能测试的重要意义 3.性能分析流程及方法 4.应用系统性能调优之性能分析 Java性能监控分析及调优工具 ...
- 软件性能测试完整指南,软件性能测试与调优指南.pdf
软件性能测试与调优指南 软件性能测试与调优指南 Page 1 of 36 版本信息 名称 编 号 1.0 拟 制 版本号 初稿 审 核 软件性能测试与调优指南 密 级 普通 共38页 批 准 更改信息 ...
- MYSQL企业常见架构与调优经验分享-高俊峰-专题视频课程
MYSQL企业常见架构与调优经验分享-8967人已学习 课程介绍 爱维Linux独家发行,从MYSQL系统安装.配置入手,从多个方面深入介绍MYSQL的使用技巧和调优策略,大限度发挥M ...
- Spark性能优化:Shuffle调优篇
Spark性能优化:Shuffle调优篇 一.调优概述 大多数Spark作业的性能主要就是消耗在了shuffle环节,因为该环节包含了大量的磁盘IO.序列化.网络数据传输等操作.因此,如果要让作业的性 ...
- GPU性能优化之CUDA调优指南
GPU性能优化之CUDA调优指南 GPU性能优化之CUDA调优指南 1 整体性能优化策略 2 最大化利用率 2.1 应用程序层次 2.2 设备层次 2.3 多处理器层次 2.3.1 占用率计算 3 最 ...
- mysql工具使用意义_MySQL性能分析、及调优工具使用详解
本文汇总了MySQL DBA日常工作中用到的些工具,方便初学者,也便于自己查阅. 先介绍下基础设施(CPU.IO.网络等)检查的工具: vmstat.sar(sysstat工具包).mpstat.op ...
- MYSQL企业常用架构与调优经验分享
小道消息:2016爱维Linux高薪实战运维提高班全新登场,课程大纲:http://www.iivey.com/666-2 一.选择Percona Server.MariaDB还是MYSQL 1.My ...
- 攻破MySQL性能瓶颈必知的调优技巧
点击蓝色"程序猿DD"关注我 回复"资源"获取独家整理的学习资料! 来源:clsn.io/clsn/lx287.html 一.前言 MySQL调优对于很多程序员 ...
最新文章
- 职工工资信息系统 c语言题,谁能帮我解决关于C语言的一些题?
- cad文本改宋体字型lisp_CAD绘图员必须掌握的15个高能技巧,别人3天工作量你半天搞定!...
- python零基础看什么视频和书籍-资料│最适合大学生零基础学的Python视频+电子书...
- Chrome浏览器插件OneTab标签聚合插件
- 《游戏编程模式》一7.8 并发状态机
- python 实现统计ftp服务器指定目录下文件夹数目、文件数目及所有文件大小 本次主要为满足应用方核对上传到ftp服务器的文件是否缺漏。 主要要求:指定目录下,文件夹数目/文件数目/所有文件大小
- 嵌入式Linux要学哪些东西?你真的造吗?
- java 动软_动软代码生成器下载_2017动软代码生成器下载及相关推荐 - noYes软件大全...
- php cpp,PHPCPP安装以及hello world
- HDU 3400 Line belt (三分)
- 命令行Terminal增加proxy开关
- React Native的缓存和下载
- 关于IllegalArgumentException occurred while calling setter for property
- 机械臂技术参数的意义
- Ardupilot环境搭建
- UOS V20 SP1 升级到Update1 后WPS无法打开
- 古典概率,条件概率,全概率
- ThinkPHP中的exp查询
- 【TED】How to get better at the things you care about?
- 最小环问题(无向图)
热门文章
- db2时间差换成月_IBM DB2计算两个时间戳记间的时间差
- 《机器视觉与算法》学习笔记(一)——图像的采集
- 华为鸿蒙系统学习笔记6-方舟编译器深度解析
- epoll的惊群效应
- Shell脚本(五)-脚本中运算符号及命令
- mysql sdo geometry_c#读写SDO_GEOMETRY字段
- Java调用金蝶接口
- Android-10-拨号器
- BadCopy Pro光盘恢复工具的使用
- cc37a_demo_C++_异常_(1)-txwtech-_打开-读取文件-写入文件-使用方法