TPCH 100G 199秒, 32c128g 1-1-1

测试流程 参考使用obd 运行tpch, 参考文档 OceanBase 社区

硬件配置:

阿里云ecs: 32core 128g, 系统盘essd 200g iops 5万, 数据盘 essd 500g 10万 iops

操作步骤:

  1. 用obd 部署1-1-1 集群, 这里一个小细节, 因为硬盘不够大, 没有使用autodeploy, 直接使用deploy, observer 内存设置为118g 内存, 系统目录和redo log 都是用系统盘, 数据目录使用数据盘
  2. 用obd 创建租户perf
  3. 创建链接

#sudo yum install -y yum-utils #sudo yum-config-manager --add-repo https://mirrors.aliyun.com/oceanbase/OceanBase.repo #sudo yum install obtpch #sudo ln -s /usr/tpc-h-tools/tpc-h-tools/ /usr/local/ #obd test tpch obperf --tenant=perf -s 100 --remote-tbl-dir=/tmp/tpch100 Get local repositories and plugins ok Open ssh connection ok Cluster status check ok Connect observer(z1(172.30.62.232):2881) ok Send tbl to remote (z1(172.30.62.232)) ok Create table ok Load data ok Merge ok Format SQL ok Warmup ok [2022-02-09 15:18:42]: start /root/tmp/db1.sql [2022-02-09 15:19:12]: end /root/tmp/db1.sql, cost 30.8s [2022-02-09 15:19:12]: start /root/tmp/db2.sql [2022-02-09 15:19:15]: end /root/tmp/db2.sql, cost 2.2s [2022-02-09 15:19:15]: start /root/tmp/db3.sql [2022-02-09 15:19:29]: end /root/tmp/db3.sql, cost 13.9s [2022-02-09 15:19:29]: start /root/tmp/db4.sql ^@[2022-02-09 15:19:30]: end /root/tmp/db4.sql, cost 1.8s [2022-02-09 15:19:30]: start /root/tmp/db5.sql [2022-02-09 15:19:42]: end /root/tmp/db5.sql, cost 12.0s [2022-02-09 15:19:42]: start /root/tmp/db6.sql [2022-02-09 15:19:48]: end /root/tmp/db6.sql, cost 5.7s [2022-02-09 15:19:48]: start /root/tmp/db7.sql [2022-02-09 15:20:00]: end /root/tmp/db7.sql, cost 11.5s [2022-02-09 15:20:00]: start /root/tmp/db8.sql [2022-02-09 15:20:06]: end /root/tmp/db8.sql, cost 6.0s [2022-02-09 15:20:06]: start /root/tmp/db9.sql [2022-02-09 15:20:40]: end /root/tmp/db9.sql, cost 33.8s [2022-02-09 15:20:40]: start /root/tmp/db10.sql [2022-02-09 15:20:56]: end /root/tmp/db10.sql, cost 16.1s [2022-02-09 15:20:56]: start /root/tmp/db11.sql [2022-02-09 15:20:57]: end /root/tmp/db11.sql, cost 1.3s [2022-02-09 15:20:57]: start /root/tmp/db12.sql [2022-02-09 15:21:04]: end /root/tmp/db12.sql, cost 7.2s [2022-02-09 15:21:04]: start /root/tmp/db13.sql [2022-02-09 15:21:09]: end /root/tmp/db13.sql, cost 5.3s [2022-02-09 15:21:09]: start /root/tmp/db14.sql [2022-02-09 15:21:11]: end /root/tmp/db14.sql, cost 1.2s [2022-02-09 15:21:11]: start /root/tmp/db15.sql [2022-02-09 15:21:13]: end /root/tmp/db15.sql, cost 2.2s [2022-02-09 15:21:13]: start /root/tmp/db16.sql [2022-02-09 15:21:15]: end /root/tmp/db16.sql, cost 2.3s [2022-02-09 15:21:15]: start /root/tmp/db17.sql [2022-02-09 15:21:22]: end /root/tmp/db17.sql, cost 6.8s [2022-02-09 15:21:22]: start /root/tmp/db18.sql ^@[2022-02-09 15:21:28]: end /root/tmp/db18.sql, cost 6.5s [2022-02-09 15:21:28]: start /root/tmp/db19.sql [2022-02-09 15:21:36]: end /root/tmp/db19.sql, cost 7.5s [2022-02-09 15:21:36]: start /root/tmp/db20.sql [2022-02-09 15:21:43]: end /root/tmp/db20.sql, cost 7.7s [2022-02-09 15:21:43]: start /root/tmp/db21.sql [2022-02-09 15:21:58]: end /root/tmp/db21.sql, cost 14.5s [2022-02-09 15:21:58]: start /root/tmp/db22.sql [2022-02-09 15:22:01]: end /root/tmp/db22.sql, cost 3.1s Total Cost: 199.4s

1 个赞

欢迎大家上传自己的测试结果

请问有没有手动执行tpcc进行压测过,我目前使用手动执行tpcc压测500G,感觉很慢啊

麻烦提供下详细的压测信息,参数配置、LOG 信息以及监控等,我们看下是否哪里有瓶颈。