|
What UnixBench that?
UnixBench is a unix system benchmark suite. UnixBench design goal is to provide a basic set of indicators for the class unix systems, so there are many projects in all aspects of performance test systems. There are various test scores, then there is a comprehensive score, so you can easily go through the score comparison.
UnixBench also contains some very simple 2D and 3D graphics tests.
UnixBench also support testing multi-CPU system, the default behavior is tested twice, the first test is a process, and the second is to test parts of N, N equals the number of CPU. This design is for the following objectives:
Single-task performance test system
Multitasking Performance Test System
Parallel processing ability of the test system
UnixBench a benchmarking tool-based system is not a simple CPU memory or disk test tools. The test results depends not only on the hardware, but also on the system, development libraries, and even the compiler.
Test Project
Dhrystone test
Testing focused on string processing, no floating-point arithmetic operations. This test is used to test the link compiler, code optimization, memory cache, wait state, the integer data types, hardware and software design will be a very big impact test results.
Whetstone test
The test program used to test the efficiency and speed of floating-point operations. The test project contains a number of typical performance scientific computing module contains a number of C language function, sin cos sqrt exp and log, and the use of integer and floating point math operations. It contains an array access, conditional branches and procedure calls.
Execl Throughput (execl throughput, where execl is the class unix system is very important function, non-office software execl) test
This test is the test number of calls per second execl function. execl is part of the exec family of functions, the use of new graphics instead of the current graphics processing. There are many commands and the front of the execve () function is very similar to the command.
File Copy Test
This test measures the file data is transferred from one file to another, using a lot of cache. Including file read, write, copy test, test targets within a certain time (default is 10 seconds) is rewritten to read, the number of characters copied.
Pipe Throughput (pipeline throughput) test
pipe is simple communication between processes. Pipeline throughput test is to test the process in a second a 512 bit write to a pipe and read back views
number. Pipeline throughput test and the actual programming gap.
Pipe-based Context Switching (context-based interactive pipeline) test
This test measures the two processes through the pipeline to increase throughput of the exchange and the number of integer multiples. Very similar to the real program based on context switching and piping. Test program to produce a two-way communication channels of child threads.
Process Creation (process creation) test
The test measures a process capable of producing sub-thread and the number of immediate withdrawal. The process of creating a new process really blocking and memory footprint, so the test program directly using the memory bandwidth. This test is used to compare a large number of typical operating system process creation.
Shell Scripts Test
shell script test used to measure in one minute, a process can start and stop times for shell scripts, typically test 1,2, 3, 4 copies together, eight shell script, shell script is a conversion data file script.
System Call Overhead (system calls consume) test
This test measures entering and leaving the consumption of the system kernel, e.g., the consumption of the system call. Procedures simple, repetitive execution getpid call (call return process id). Consumption indicator is to call entering and leaving the execution time kernel.
(Graphic) Graphical Tests Test
By the "ubgears" program composed of very coarse test of 2D and 3D graphics performance, especially the 3D test is very limited. The test results and hardware systems suitable drive a great relationship.
UnixBench installation
wget http://byte-unixbench.googlecode.com/files/unixbench-5.1.2.tar.gz
tar xvfz unixbench-5.1.2.tar.gz
cd unixbench-5.1.2
If this line does not need to test graphics, comment out the Makefile
#GRAPHIC_TESTS = Defined
run
./Run
Test Results
# # # # # # # # # #### # ##### # ######
# # # # # # # # # # # # # # # # # #
# # # # # # # # # # # # ##### ##### ######
# # # # # # # # # # # # # # # # #
# # # # # # # # # # # # # # # # # #
#### # # # # # # # #### # ##### # ######
Version 5.1.2 Based on the Byte Magazine Unix Benchmark
Multi-CPU version Version 5 revisions by Ian Smith,
Sunnyvale, CA, USA
December 22, 2007 johantheghost at yahoo period com
1 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10
1 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10
1 x Execl Throughput 1 2 3
1 x File Copy 1024 bufsize 2000 maxblocks 1 2 3
1 x File Copy 256 bufsize 500 maxblocks 1 2 3
1 x File Copy 4096 bufsize 8000 maxblocks 1 2 3
1 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10
1 x Pipe-based Context Switching 1 2 3 4 5 6 7 8 9 10
1 x Process Creation 1 2 3
1 x System Call Overhead 1 2 3 4 5 6 7 8 9 10
1 x Shell Scripts (1 concurrent) 1 2 3
1 x Shell Scripts (8 concurrent) 1 2 3
================================================== ======================
BYTE UNIX Benchmarks (Version 5.1.2)
System: localhost.localdomain: GNU / Linux
OS: GNU / Linux - 3.10.0-123.8.1.el7.x86_64 - # 1 SMP Mon Sep 22 19:06:58 UTC 2014
Machine: x86_64 (x86_64)
Language: en_US.utf8 (charmap = "UTF-8", collate = "UTF-8")
CPU 0: Intel (R) Xeon (R) CPU X5650 @ 2.67GHz (5331.8 bogomips)
x86-64, MMX, Physical Address Ext, SYSENTER / SYSEXIT, SYSCALL / SYSRET, Intel virtualization
08:24:54 up 1 day, 2:11, 1 user, load average: 0.00, 0.01, 0.05; runlevel 3
-------------------------------------------------- ----------------------
Benchmark Run: Wed Nov 12 2014 08:24:54 - 08:52:53
1 CPU in system; running 1 parallel copy of tests
Dhrystone 2 using register variables 28890881.0 lps (10.0 s, 7 samples)
Double-Precision Whetstone 3880.4 MWIPS (9.0 s, 7 samples)
Execl Throughput 4146.3 lps (30.0 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 1051084.3 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 286552.2 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 2142638.4 KBps (30.0 s, 2 samples)
Pipe Throughput 1726807.0 lps (10.0 s, 7 samples)
Pipe-based Context Switching 322865.5 lps (10.0 s, 7 samples)
Process Creation 13662.4 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 5955.4 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 713.1 lpm (60.0 s, 2 samples)
System Call Overhead 2138318.1 lps (10.0 s, 7 samples)
System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 28890881.0 2475.7
Double-Precision Whetstone 55.0 3880.4 705.5
Execl Throughput 43.0 4146.3 964.2
File Copy 1024 bufsize 2000 maxblocks 3960.0 1051084.3 2654.3
File Copy 256 bufsize 500 maxblocks 1655.0 286552.2 1731.4
File Copy 4096 bufsize 8000 maxblocks 5800.0 2142638.4 3694.2
Pipe Throughput 12440.0 1726807.0 1388.1
Pipe-based Context Switching 4000.0 322865.5 807.2
Process Creation 126.0 13662.4 1084.3
Shell Scripts (1 concurrent) 42.4 5955.4 1404.6
Shell Scripts (8 concurrent) 6.0 713.1 1188.4
System Call Overhead 15000.0 2138318.1 1425.5
========
System Benchmarks Index Score 1444.7 |
|
|
|