UnixBench算分介绍
??关于如何用UnixBench,介绍文章很多,这里就不展开了。这里重点描述下它是如何算分的。 运行参数碰到很多客户,装好后,直接./Run,就把结果跑出来了,然后还只取最后一个分值,比谁高谁低。 ------------------------------------------------------------------------ Benchmark Run: 一 6月 25 2018 20:25:47 - 20:54:19 4 CPUs in system; running 1 parallel copy of tests Dhrystone 2 using register variables 30971628.9 lps (10.0 s,7 samples) Double-Precision Whetstone 3928.1 MWIPS (12.4 s,7 samples) Execl Throughput 3117.6 lps (30.0 s,2 samples) File Copy 1024 bufsize 2000 maxblocks 645027.2 KBps (30.0 s,2 samples) File Copy 256 bufsize 500 maxblocks 229505.4 KBps (30.0 s,2 samples) File Copy 4096 bufsize 8000 maxblocks 1288742.6 KBps (30.0 s,2 samples) Pipe Throughput 1635960.9 lps (10.0 s,7 samples) Pipe-based Context Switching 337333.8 lps (10.0 s,7 samples) Process Creation 8238.2 lps (30.0 s,2 samples) Shell Scripts (1 concurrent) 5817.0 lpm (60.0 s,2 samples) Shell Scripts (8 concurrent) 2183.9 lpm (60.0 s,2 samples) System Call Overhead 2465754.7 lps (10.0 s,7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 30971628.9 2654.0 Double-Precision Whetstone 55.0 3928.1 714.2 Execl Throughput 43.0 3117.6 725.0 File Copy 1024 bufsize 2000 maxblocks 3960.0 645027.2 1628.9 File Copy 256 bufsize 500 maxblocks 1655.0 229505.4 1386.7 File Copy 4096 bufsize 8000 maxblocks 5800.0 1288742.6 2222.0 Pipe Throughput 12440.0 1635960.9 1315.1 Pipe-based Context Switching 4000.0 337333.8 843.3 Process Creation 126.0 8238.2 653.8 Shell Scripts (1 concurrent) 42.4 5817.0 1371.9 Shell Scripts (8 concurrent) 6.0 2183.9 3639.9 System Call Overhead 15000.0 2465754.7 1643.8 ======== System Benchmarks Index Score 1362.9 ------------------------------------------------------------------------ Benchmark Run: 一 6月 25 2018 20:54:19 - 21:22:54 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 114984418.6 lps (10.0 s,7 samples) Double-Precision Whetstone 16614.2 MWIPS (11.6 s,7 samples) Execl Throughput 13645.3 lps (30.0 s,2 samples) File Copy 1024 bufsize 2000 maxblocks 751698.4 KBps (30.0 s,2 samples) File Copy 256 bufsize 500 maxblocks 230211.7 KBps (30.0 s,2 samples) File Copy 4096 bufsize 8000 maxblocks 1964420.6 KBps (30.0 s,2 samples) Pipe Throughput 5999380.0 lps (10.0 s,7 samples) Pipe-based Context Switching 1095000.2 lps (10.0 s,7 samples) Process Creation 34454.9 lps (30.0 s,2 samples) Shell Scripts (1 concurrent) 18218.1 lpm (60.0 s,2 samples) Shell Scripts (8 concurrent) 2493.1 lpm (60.0 s,2 samples) System Call Overhead 5643267.3 lps (10.0 s,7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 114984418.6 9853.0 Double-Precision Whetstone 55.0 16614.2 3020.8 Execl Throughput 43.0 13645.3 3173.3 File Copy 1024 bufsize 2000 maxblocks 3960.0 751698.4 1898.2 File Copy 256 bufsize 500 maxblocks 1655.0 230211.7 1391.0 File Copy 4096 bufsize 8000 maxblocks 5800.0 1964420.6 3386.9 Pipe Throughput 12440.0 5999380.0 4822.7 Pipe-based Context Switching 4000.0 1095000.2 2737.5 Process Creation 126.0 34454.9 2734.5 Shell Scripts (1 concurrent) 42.4 18218.1 4296.7 Shell Scripts (8 concurrent) 6.0 2493.1 4155.1 System Call Overhead 15000.0 5643267.3 3762.2 ======== System Benchmarks Index Score 3357.0 很多人就拿了3357那个分数去比了,但是上面那个单进程结果1362.9也有意义,但凡接触了这么多案例,没人关心过。多进程结果就是根据系统CPU核数,同时起多个进程的结果;单进程就是只起一个进程的结果,对于系统性能来说,两个结果都是有意义的。 "dhry2reg","whetstone-double","execl", "fstime","fsbuffer","fsdisk","pipe","context1","spawn","shell1","shell8","syscall" 对应的就是上面的结果的各个结果对应的case了。
算分每个小程序在执行的时候都需要指定迭代模式和执行时间以及并发情况,所有的进程一次执行的结果都是统一模式。 单进程算分:下面是单进程的一个举例: Process Creation -- 1 copy ==> "/opt/unixbench/UnixBench/pgms/spawn" 30 2>&1 >> "/opt/unixbench/UnixBench/results/VM_0_13_centos-2018-06-25-05.log" #### Pass 1 # COUNT0: 247371 #分数 # COUNT1: 1 # timebase 程序写死 # COUNT2: lps # 测试项名称 # elapsed: 30.003119 # 耗时 # pid: 16803 # 进程ID # status: 0 # 是否成功退出 #### Pass 2 # COUNT0: 242919 # COUNT1: 1 # COUNT2: lps # elapsed: 30.002898 # pid: 5035 # status: 0 #### Pass 3 # COUNT0: 243989 # COUNT1: 1 # COUNT2: lps # elapsed: 30.002732 # pid: 21228 # status: 0 *Dump score: 242919.0 Count score: 243989.0 Count score: 247371.0 >>>> Results of 1 copy >>>> score: 8188.34084738901 >>>> time: 30.0029255 >>>> iterations: 2 其中COUNT0,COUNT1,COUNT2是这么算出来的,每个进程的结果如: COUNT|x|y|x 经过解析,变成如下: COUNT0 = x COUNT1 = y COUNT2 = z 算分过程如下:
多进程算分那如果并发执行多个呢?举例如下: Shell Scripts (1 concurrent) -- 4 copies ==> "/opt/unixbench/UnixBench/pgms/looper" 60 "/opt/unixbench/UnixBench/pgms/multi.sh" 1 2>&1 >> "/opt/unixbench/UnixBench/results/VM_0_13_centos-2018-06-25-05.log" #### Pass 1 # COUNT0: 4614 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.005639 # pid: 20858 # status: 0 # COUNT0: 4596 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.009496 # pid: 20859 # status: 0 # COUNT0: 4592 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.011761 # pid: 20862 # status: 0 # COUNT0: 4614 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.011930 # pid: 20864 # status: 0 #### Pass 2 # COUNT0: 4547 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.005597 # pid: 10791 # status: 0 # COUNT0: 4590 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.013270 # pid: 10793 # status: 0 # COUNT0: 4578 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.006054 # pid: 10794 # status: 0 # COUNT0: 4561 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.014214 # pid: 10797 # status: 0 #### Pass 3 # COUNT0: 4631 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.013816 # pid: 31734 # status: 0 # COUNT0: 4632 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.012614 # pid: 31735 # status: 0 # COUNT0: 4637 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.005633 # pid: 31737 # status: 0 # COUNT0: 4645 # COUNT1: 60 # COUNT2: lpm # elapsed: 60.006082 # pid: 31740 # status: 0 *Dump score: 18276.0 Count score: 18416.0 Count score: 18545.0 >>>> Sum of 4 copies >>>> score: 18477.4244713467 >>>> time: 60.009621375 >>>> iterations: 2 算分过程如下:
总分那文章开头多进程的图例分数举例:
综上对UnixBench的分数计算算是全面介绍了一边,附件有excel证明计算过程。 附件下载:??算分过程.xls...[米拉齐].1543830848.zip ? 阅读原文??????? 更多技术干货 请关注阿里云云栖社区微信号 :yunqiinsight (编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |