你的位置： >
> sysbench Linux下的性能测试工具
sysbench是一款开源的多线程性能测试工具，可以执行CPU/内存/线程/IO/数据库等方面的性能测试。数据库目前支持MySQL /Oracle/PostgreSQL。本文只是简单演示一下几种测试的用法，后续准备利用sysbench来对MySQL进行一系列的测试。具体的一些 参数设置，需要根据不同的测试要求来进行调整.
-c http://sourceforge.net/projects/sysbench/files/sysbench/0.4.12/sysbench-0.4.12.tar.gz/download
sysbench-0.4.12.tar.gz
#cd sysbench-0.4.12
#./configure && make && make install
如果需要测试Oracle/PostgreSQL，则在configure时需要加上–with-oracle或者–with-pgsql参数
[root@localhost sysbench]# ./sysbench
sysbench [general-options]… –test=&test-name& [test-options]… command
–num-threads=N
创建测试线程的数目。默认为1.
–max-requests=N
请求的最大数目。默认为10000，0代表不限制。
–max-time=N
最大执行时间，单位是s。默认是0,不限制。
–forced-shutdown=STRING
超过max-time强制中断。默认是off。]
–thread-stack-size=SIZE
每个线程的堆栈大小。默认是32K。
–init-rng=[on|off]
在测试开始时是否初始化随机数发生器。默认是off。
–test=STRING
指定测试项目名称。
–debug=[on|off]
是否显示更多的调试信息。默认是off。
–validate=[on|off]
在可能情况下执行验证检查。默认是off。
fileio – File I/O test
cpu – CPU performance test
memory – Memory functions speed test
threads – Threads subsystem performance test
mutex – Mutex performance test(互斥性能测试)
oltp – OLTP test
指令: prepare(测试前准备工作) run(正式测试) cleanup(测试后删掉测试数据) help version
See ‘sysbench –test=&name& help’ for a list of options for each test. 查看每个测试项目的更多选项列表。
[root@localhost bin]# ./sysbench –test=fileio help
–file-num=N
创建测试文件的数量。默认是128
–file-block-size=N
测试时文件块的大小。默认是16384(16K)
–file-total-size=SIZE
测试文件的总大小。默认是2G
–file-test-mode=STRING
文件测试模式{seqwr(顺序写), seqrewr(顺序读写), seqrd(顺序读), rndrd(随机读), rndwr(随机写), rndrw(随机读写)}
–file-io-mode=STRING
文件操作模式{sync(同步),async(异步),fastmmap(快速map映射),slowmmap(慢map映射)}。默认是sync
–file-extra-flags=STRING
使用额外的标志来打开文件{sync,dsync,direct} 。默认为空
–file-fsync-freq=N
执行fsync()的频率。(0 – 不使用fsync())。默认是100
–file-fsync-all=[on|off] 每执行完一次写操作就执行一次fsync。默认是off
–file-fsync-end=[on|off] 在测试结束时才执行fsync。默认是on
–file-fsync-mode=STRING
使用哪种方法进行同步{fsync, fdatasync}。默认是fsync
–file-merged-requests=N
如果可以，合并最多的IO请求数(0 – 表示不合并)。默认是0
–file-rw-ratio=N
测试时的读写比例。默认是1.5
[root@localhost bin]# ./sysbench –test=cpu help
–cpu-max-prime=N
最大质数发生器数量。默认是10000
[root@localhost bin]# ./sysbench –test=memory help
–memory-block-size=SIZE
测试时内存块大小。默认是1K
–memory-total-size=SIZE
传输数据的总大小。默认是100G
–memory-scope=STRING
内存访问范围{global,local}。默认是global
–memory-hugetlb=[on|off]
从HugeTLB池内存分配。默认是off
–memory-oper=STRING
内存操作类型。{read, write, none} 默认是write
–memory-access-mode=STRING存储器存取方式{seq,rnd} 默认是seq
[root@localhost bin]# ./sysbench –test=threads help
–thread-yields=N
每个请求产生多少个线程。默认是1000
–thread-locks=N
每个线程的锁的数量。默认是8
[root@localhost bin]# ./sysbench –test=mutex help
–mutex-num=N
数组互斥的总大小。默认是4096
–mutex-locks=N
每个线程互斥锁的数量。默认是50000
–mutex-loops=N
内部互斥锁的空循环数量。默认是10000
[root@localhost bin]# ./sysbench –test=oltp help
oltp options:
–oltp-test-mode=STRING
执行模式{simple,complex(advanced transactional),nontrx(non-transactional),sp}。默认是complex
–oltp-reconnect-mode=STRING 重新连接模式{session(不使用重新连接。每个线程断开只在测试结束),transaction(在每次事务结束后重新连接),query(在每个 SQL语句执行完重新连接),random(对于每个事务随机选择以上重新连接模式)}。默认是session
–oltp-sp-name=STRING
存储过程的名称。默认为空
–oltp-read-only=[on|off]
只读模式。Update，delete，insert语句不可执行。默认是off
–oltp-skip-trx=[on|off]
省略begin/commit语句。默认是off
–oltp-range-size=N
查询范围。默认是100
–oltp-point-selects=N
number of point selects [10]
–oltp-simple-ranges=N
number of simple ranges [1]
–oltp-sum-ranges=N
number of sum ranges [1]
–oltp-order-ranges=N
number of ordered ranges [1]
–oltp-distinct-ranges=N
number of distinct ranges [1]
–oltp-index-updates=N
number of index update [1]
–oltp-non-index-updates=N
number of non-index updates [1]
–oltp-nontrx-mode=STRING
查询类型对于非事务执行模式{select, update_key, update_nokey, insert, delete} [select]
–oltp-auto-inc=[on|off]
AUTO_INCREMENT是否开启。默认是on
–oltp-connect-delay=N
在多少微秒后连接数据库。默认是10000
–oltp-user-delay-min=N
每个请求最短等待时间。单位是ms。默认是0
–oltp-user-delay-max=N
每个请求最长等待时间。单位是ms。默认是0
–oltp-table-name=STRING
测试时使用到的表名。默认是sbtest
–oltp-table-size=N
测试表的记录数。默认是10000
–oltp-dist-type=STRING
分布的随机数{uniform(均匀分布),Gaussian(高斯分布),special(空间分布)}。默认是special
–oltp-dist-iter=N
产生数的迭代次数。默认是12
–oltp-dist-pct=N
值的百分比被视为’special’ (for special distribution)。默认是1
–oltp-dist-res=N
‘special’的百分比值。默认是75
General database options:
–db-driver=STRING
指定数据库驱动程序(‘help’ to get list of available drivers)
–db-ps-mode=STRING编制报表使用模式{auto, disable} [auto]
Compiled-in database drivers:
mysql – MySQL driver
mysql options:
–mysql-host=[LIST,…]
MySQL server host [localhost]
–mysql-port=N
MySQL server port [3306]
–mysql-socket=STRING
MySQL socket
–mysql-user=STRING
MySQL user [sbtest]
–mysql-password=STRING
MySQL password []
–mysql-db=STRING
MySQL database name [sbtest]
–mysql-table-engine=STRING
storage engine to use for the test table {myisam,innodb,bdb,heap,ndbcluster,federated} [innodb]
–mysql-engine-trx=STRING
whether storage engine used is transactional or not {yes,no,auto} [auto]
–mysql-ssl=[on|off]
use SSL connections, if available in the client library [off]
–myisam-max-rows=N
max-rows parameter for MyISAM tables [1000000]
–mysql-create-options=STRING additional options passed to CREATE TABLE []
1、CPU测试
[root@localhost bin]# ./sysbench –test=cpu –cpu-max-prime=20000 run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Number of threads: 1
Doing CPU performance benchmark
Threads started!
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time:
total number of events:
total time taken by event execution: 31.9334
per-request statistics:
95 percentile:
Threads fairness:
events (avg/stddev):
execution time (avg/stddev):
2、线程数测试
thread-locks小于线程数除以2，lock越少，处理时间越长。
# ./sysbench –test=threads –num-threads=512 –thread-yields=100 –thread-locks=2 run
sysbench 0.4.12:
multi-threaded system evaluation benchmark
Running the test with following options:Number of threads: 512
Doing thread subsystem performance test
Thread yields per test: 100 Locks used: 2
Threads started!
WARNING: Operation time (0.000000) is less than minimal counted value, counting as 1.000000
WARNING: Percentile statistics will be inaccurateDone.
Test execution summary:
total time:
total number of events:
total time taken by event execution:
per-request statistics:
95 percentile:
Threads fairness:
events (avg/stddev):
execution time (avg/stddev):
3、磁盘IO性能测试
首先生成需要的测试文件，文件总大小3G，16个并发线程，随机读写模式。执行完后会在当前目录下生成一堆小文件。
# ./sysbench –test=fileio –num-threads=16 –file-total-size=3G –file-test-mode=rndrw prepare
sysbench 0.4.12:
multi-threaded system evaluation benchmark
128 files, 24576Kb each, 3072Mb total
Creating files for the test…
开始测试：
# ./sysbench –test=fileio –num-threads=16 –file-total-size=3G –file-test-mode=rndrw run
sysbench 0.4.12:
multi-threaded system evaluation benchmark
Running the test with following options:Number of threads: 16
Extra file open flags: 0
128 files, 24Mb each
3Gb total file size
Block size 16Kb
Number of random requests for random IO: 10000
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests
.Calling fsync() at the end of test, Enabled.
Using synchronous I/O modeDoing random r/w test
Threads started!
WARNING: Operation time (0.000000) is less than minimal counted value, counting as 1.000000
WARNING: Percentile statistics will be inaccurateDone.
Operations performed:
6004 Read, 3996 Write, 12800 Other = 22800 TotalRead 93.812Mb
Written 62.438Mb
Total transferred 156.25Mb
(6.472Mb/sec)
414.21 Requests/sec executed
Test execution summary:
total time:
total number of events:
total time taken by event execution: 164.4243
per-request statistics:
95 percentile:
Threads fairness:
events (avg/stddev):
xecution time (avg/stddev):
# ./sysbench –test=fileio –num-threads=16 –file-total-size=3G –file-test-mode=rndrw cleanup
sysbench 0.4.12:
multi-threaded system evaluation benchmark
Removing test files…
4、内存测试
下面的参数指定了本次测试整个过程是在内存中传输 1G 的数据量，每个 block 大小为 8K。
./sysbench –test=memory –num-threads=64 –memory-block-size=8192 –memory-total-size=1G run
sysbench 0.4.12:
multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 64
Doing memory operations speed test
Memory block size: 8K
Memory transfer size: 1024M
Memory operations type: writeMemory scope type: globalThreads started!(last message repeated 1 times)
WARNING: Operation time (0.000000) is less than minimal counted value, counting as 1.000000
WARNING: Percentile statistics will be inaccurate(last message repeated 1 times)Done.
Operations performed: 6391.08 ops/sec)
1024.00 MB transferred (3253.06 MB/sec)
Test execution summary:
total time:
total number of events:
total time taken by event execution: 17.5553
per-request statistics:
95 percentile:
Threads fairness:
events (avg/stddev):
execution time (avg/stddev):
5、Mutex测试
[root@localhost ]# ./sysbench –test=mutex –num-threads=1500 –max-requests=2000
–mutex-num=10240 –mutex-locks=100000
–mutex-loops=15000 run
sysbench 0.4.12:
multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1500
Doing mutex performance test
Threads started!
Test execution summary:
total time:
total number of events:
total time taken by event execution:
per-request statistics:
13770.44ms
95 percentile:
12489.67ms
Threads fairness:
events (avg/stddev):
execution time (avg/stddev):
6、MySQL数据库测试
首先需要创建默认的sbtest数据库,或者使用–mysql-db指定一个已经存在的数据库
生成测试数据，引擎为myisam,表大小为1000000条记录
[root@localhost ]# ./sysbench --test=oltp --mysql-table-engine=myisam --oltp-table-size=1000000
--mysql-user=root --mysql-socket=/opt/mysql/run/mysql.sock prepare
sysbench 0.4.12:
multi-threaded system evaluation benchmark
No DB drivers specified, using mysql
Creating table 'sbtest'...
Creating 1000000 records in table 'sbtest'...
root@sbtest 11:42:18&desc sbtest.
+-------+------------------+------+-----+---------+----------------+
| Field | Type
| Null | Key | Default | Extra
+-------+------------------+------+-----+---------+----------------+
| int(10) unsigned | NO
| PRI | NULL
| auto_increment |
| int(10) unsigned | NO
| char(120)
| char(60)
+-------+------------------+------+-----+---------+----------------+
[root@localhost ]# ./sysbench --test=oltp --mysql-table-engine=myisam --oltp-table-size=1000000
--mysql-user=root --mysql-socket=/opt/mysql/run/mysql.sock run
sysbench 0.4.12:
multi-threaded system evaluation benchmark
No DB drivers specified, using mysql
Running the test with following options:
Number of threads: 1
Doing OLTP test.
Running mixed OLTP test
Using Special distribution (12 iterations,
1 pct of values are returned in 75 pct cases)
Using &LOCK TABLES WRITE& for starting transactions
Using auto_inc on the id column
Maximum number of requests for OLTP test is limited to 10000
Threads started!
OLTP test statistics:
queries performed:
transactions:
(336.64 per sec.)
deadlocks:
(0.00 per sec.)
read/write requests:
96.11 per sec.)
other operations:
(673.27 per sec.)
Test execution summary:
total time:
total number of events:
total time taken by event execution: 29.6301
per-request statistics:
95 percentile:
Threads fairness:
events (avg/stddev):
execution time (avg/stddev):
[root@localhost ]# ./sysbench--test=oltp --mysql-table-engine=myisam --oltp-table-size=1000000
--mysql-user=root --mysql-socket=/opt/mysql/run/mysql.sock cleanup
sysbench 0.4.12:
multi-threaded system evaluation benchmark
No DB drivers specified, using mysql
Dropping table 'sbtest'...
转载请注明： &关于mysql读写分离测试2 - 推酷
关于mysql读写分离测试2
前一篇的测试，基本上杯具了！今天含林（运维大牛），告诉我另外一个基于MySQL协议的数据库中间层项目：Atlas
Atlas是由 Qihoo 360公司Web平台部基础架构团队开发维护的一个基于MySQL协议的数据中间层项目。它在MySQL官方推出的MySQL-Proxy 0.8.2版本的基础上，修改了大量bug，添加了很多功能特性。目前该项目在360公司内部得到了广泛应用，很多MySQL业务已经接入了Atlas平台，每天承载的读写请求数达几十亿条。
主要功能：
1.读写分离
2.从库负载均衡
4.自动分表
5.DBA可平滑上下线DB
6.自动摘除宕机的DB
二、Atlas相对于官方MySQL-Proxy的优势
1.将主流程中所有Lua代码用C重写，Lua仅用于管理接口
2.重写网络模型、线程模型
3.实现了真正意义上的连接池
4.优化了锁机制，性能提高数十倍
三、Atlas详细说明
1.Atlas的安装
2.Atlas的运行及常见问题
3.Atlas的分表功能简介
4.Atla部分配置参数及原理详解
5.Atlas的架构
6.Atlas的性能测试
7.Atlas功能特点FAQ
四、Atlas的需求及Bug反馈方式
如果用户在实际的应用场景中对Atlas有新的功能需求，或者在使用Atlas的过程中发现了bug，欢迎用户发邮件至zhuchao[，与我们取得联系，我们将及时回复。另外有热心网友建立了QQ群，开发者也已经加入，方便讨论。
五、名字来源
Atlas：希腊神话中双肩撑天的巨人，普罗米修斯的兄弟，最高大强壮的神之一，因反抗宙斯失败而被罚顶天。我们期望这个系统能够脚踏后端DB，为前端应用撑起一片天。
Atlas的安装非常简单，从/Qihoo360/Atlas/releases地址下载相应的rpm包直接安装即可，可能有一些依赖关系，yum都能解决的，就不多讲了！
七、配置文件：
配置文件位置/usr/local/mysql-proxy/config下面，就我的内网应用而言，我创建新的配置文件如下：
[mysql-proxy]
#带#号的为非必需的配置项目
#管理接口的用户名
admin-username = admin
#管理接口的密码
admin-password = passw0rd
#Atlas后端连接的MySQL主库的IP和端口，可设置多项，用逗号分隔
proxy-backend-addresses = 192.168.1.66:3306
#Atlas后端连接的MySQL从库的IP和端口，@后面的数字代表权重，用来作负载均衡，若省略则默认为1，可设置多项，用逗号分隔
proxy-read-only-backend-addresses = 192.168.1.64:.1.244:3306
#用户名与其对应的加密过的MySQL密码，密码使用PREFIX/bin目录下的加密程序encrypt加密，下行的user1和user2为示例，将其替换为你的MySQL的用户名和加密密码！
#pwds = user1:+jKsgB3YAG8=, user2:GS+tr4TPgqc=
pwds = root:FYCDJMDki+SiquyHfJnWyQ==
#设置Atlas的运行方式，设为true时为守护进程方式，设为false时为前台方式，一般开发调试时设为false，线上运行时设为true
daemon = true
#设置Atlas的运行方式，设为true时Atlas会启动两个进程，一个为monitor，一个为worker，monitor在worker意外退出后会自动将其重启，设为false时只有worker，没有monitor，一般开发调试时设为false，线上运行时设为true
keepalive = true
#工作线程数，对Atlas的性能有很大影响，可根据情况适当设置
event-threads = 64
#日志级别，分为message、warning、critical、error、debug五个级别
log-level = message
#日志存放的路径
log-path = /usr/local/mysql-proxy/log
#SQL日志的开关，可设置为OFF、ON、REALTIME，OFF代表不记录SQL日志，ON代表记录SQL日志，REALTIME代表记录SQL日志且实时写入磁盘，默认为OFF
#sql-log = OFF
#实例名称，用于同一台机器上多个Atlas实例间的区分
#instance = test
#Atlas监听的工作接口IP和端口
proxy-address = 0.0.0.0:1234
#Atlas监听的管理接口IP和端口
admin-address = 0.0.0.0:2345
#分表设置，此例中person为库名，mt为表名，id为分表字段，3为子表数量，可设置多项，以逗号分隔，若不分表则不需要设置该项
#tables = person.mt.id.3
#默认字符集，设置该项后客户端不再需要执行SET NAMES语句
#charset = utf8
#允许连接Atlas的客户端的IP，可以是精确IP，也可以是IP段，以逗号分隔，若不设置该项则允许所有IP连接，否则只允许列表中的IP连接
#client-ips = 127.0.0.1, 192.168.1
#Atlas前面挂接的LVS的物理网卡的IP(注意不是虚IP)，若有LVS且设置了client-ips则此项必须设置，否则可以不设置
#lvs-ips = 192.168.1.1
八、启动关闭重启：
# /usr/local/mysql-proxy/bin/mysql-proxyd instance start
# /usr/local/mysql-proxy/bin/mysql-proxyd instance stop
# /usr/local/mysql-proxy/bin/mysql-proxyd instance restart
九、负载读写分离测试：
[root@YQD-Intranet-DB-NO2 ~]# mysql -uroot -p***** -h192.168.1.63 -P1234
Welcome to the MySQL monitor.
Your MySQL connection id is
Server version: 5.0.81-log Source distribution
Copyright (c)
Percona LLC and/or its affiliates
Copyright (c) , Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
Type '' or '\h' for help. Type '\c' to clear the current input statement.
root@(none) 10:28:46&show variables like &server_id&;
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| server_id
+---------------+-------+
1 row in set (0.00 sec)
root@(none) 10:28:48&show variables like &server_id&;
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| server_id
+---------------+-------+
1 row in set (0.00 sec)
OLTP基准测试：
OLTP基准测试模拟了一个简单的的事务处理系统的工作负载。下面的例子使用的是一张百万行记录的表，第一步先生成这张表：
# time sysbench --test=oltp --db-driver=mysql --mysql-engine-trx=yes --mysql-table-engine=innodb --mysql-host=127.0.0.1 --mysql-port=1234 --mysql-user=root --mysql-password=****** --oltp-table-size=1000000 prepare
sysbench 0.4.12:
multi-threaded system evaluation benchmark
Creating table 'sbtest'...
Creating 1000000 records in table 'sbtest'...
real 0m58.132s
user 0m0.209s
sys 0m0.036s
接下来可以运行测试，这个例子采用了16个并发线程，只读模拟测试：
# time sysbench --test=oltp --db-driver=mysql --mysql-engine-trx=yes --mysql-table-engine=innodb --mysql-host=127.0.0.1 --mysql-port=1234 --oltp-read-only=on --mysql-user=root --mysql-password=****** --oltp-table-size=1000000 --num-threads=16 run
sysbench 0.4.12:
multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 16
Doing OLTP test.
Running mixed OLTP test
Doing read-only test
Using Special distribution (12 iterations,
1 pct of values are returned in 75 pct cases)
Using &BEGIN& for starting transactions
Using auto_inc on the id column
Maximum number of requests for OLTP test is limited to 10000
Threads started!
OLTP test statistics:
queries performed:
transactions:
(1007.89 per sec.)
deadlocks:
(0.00 per sec.)
read/write requests:
110.48 per sec.)
other operations:
(2015.78 per sec.)
Test execution summary:
total time:
total number of events:
total time taken by event execution: 158.5972
per-request statistics:
95 percentile:
Threads fairness:
events (avg/stddev):
execution time (avg/stddev):
real 0m10.198s
user 0m1.216s
sys 0m2.583s
从时间上来看比之前haproxy测试要略慢,还是haproxy的性能更靠谱，但是haproxy需要在应用层实现读写分离，就是代码了
tpcc压测：
root@(none) 10:46:19&create database tpcc5;
Query OK, 1 row affected (0.54 sec)
# mysql -uroot -p******* -h192.168.1.63 -P1234 tpcc5 & create_table.sql
Warning: Using a password on the command line interface can be insecure.
ERROR ) at line 140: Variable 'foreign_key_checks' can't be set to the value of 'NULL'
# mysql -uroot -p******* -h192.168.1.63 -P1234 tpcc5 & add_fkey_idx.sql
Warning: Using a password on the command line interface can be insecure.
ERROR ) at line 23: Variable 'foreign_key_checks' can't be set to the value of 'NULL'
tpcc导入表时出错了，提示变量foreign_key_checks不能设置为NULL值，暂且不管它，继续测试：
# ./tpcc_load 192.168.1.63:1234 tpcc5 root &********& 3
*************************************
*** ###easy### TPC-C Data Loader
*************************************
&Parameters&
[server]: 192.168.1.63
[port]: 1234
[DBname]: tpcc5
[user]: root
[pass]: LVS@071103
[warehouse]: 3
TPCC Data Load Started...
Loading Item
.................................................. 5000
.................................................. 10000
.................................................. 15000
.................................................. 20000
.................................................. 25000
.................................................. 30000
.................................................. 35000
.................................................. 40000
.................................................. 45000
.................................................. 50000
下面省略N行.......................................
# ./tpcc_start -h192.168.1.63 -P1234 -dtpcc5 -uroot -p******** -w3 -c32 -r10 -l600
***************************************
*** ###easy### TPC-C Load Generator ***
***************************************
中间省略N行.................................................
&Raw Results&
[0] sc:5059
[1] sc:5057
[2] sc:506
[3] sc:506
[4] sc:506
in 600 sec.
&Raw Results2(sum ver.)&
[0] sc:5059
[1] sc:5059
[2] sc:506
[3] sc:506
[4] sc:506
&Constraint Check& (all must be [OK])
[transaction percentage]
Payment: 43.47% (&=43.0%) [OK]
Order-Status: 4.35% (&= 4.0%) [OK]
Delivery: 4.35% (&= 4.0%) [OK]
Stock-Level: 4.35% (&= 4.0%) [OK]
[response time (at least 90% passed)]
New-Order: 100.00%
Payment: 100.00%
Order-Status: 100.00%
Delivery: 100.00%
Stock-Level: 100.00%
505.900 TpmC
已发表评论数()
请填写推刊名
描述不能大于100个字符!
权限设置： 公开
仅自己可见
正文不准确
标题不准确
排版有问题
主题不准确
没有分页内容
图片无法显示
视频无法显示
与原文不一致