Detailed description of the running software UnixBench

Detailed description of the running software UnixBench

What is unixworkflow?

UnixBench is a set of unix system benchmarking kits. UnixBench is designed to provide a set of basic metrics for unix-like systems. Therefore, many projects test system performance. Each test has a score, and then has a comprehensive score, which can be easily compared by the score.

UnixBench also contains some very simple 2D and 3D graphic tests.

UnixBench also supports multi-CPU system tests. The default behavior is to test twice. The first is a process test, the second is N tests, and N is equal to the number of CPUs. This design aims:

• Test the system's single-task performance
• Test the system's multi-task performance
• Test the system's parallel processing capability

UnixBench is a system-based Benchmark Testing Tool, not simply a CPU memory or disk testing tool. The test results depend not only on the hardware, but also on the system, development library, and even the compiler.

Test Item

Dhrystone Testing

The test focuses on string processing without floating point operations. This test is used to test the linker compilation, code optimization, memory cache, Wait Status, integer data type, and so on. both hardware and software design greatly affect the test results.

Whetstone Test

This test item is used to test the efficiency and speed of floating point operations. This test project contains several typical performance modules for scientific computing, including a large number of C functions, sin cos sqrt exp and logs, and mathematical operations using integers and floating points. Contains array access, condition branches, and process calls.

Execl Throughput (execl Throughput, where execl is a very important function in unix-like systems, non-office software execl) Testing

The number of execl function calls per second in this test. Execl is part of the exec function family and replaces the current graph processing with New Graph processing. Many Commands are very similar to execve () function commands on the front end.

File Copy test

This test measures that file data is transferred from one file to another and uses a large amount of cache. This includes file read, write, and copy tests. The test indicator is the number of characters that are overwritten, read, and copied in a certain period of time (10 seconds by default.

Pipe Throughput (pipeline Throughput) test

Pipe is the communication between simple processes. The pipeline throughput test is the number of times that a process writes 512 bits to a pipeline in one second and reads back.

Number. There is a gap between Pipeline Throughput testing and actual programming.

Pipe-based Context Switching (pipeline-based Context interaction) test

This test measures the number of times two processes increase throughput through pipeline switching and integer multiples. Pipeline-based context switching is similar to real programs. The test program generates a subthread for two-way pipeline communication.

Process Creation (Process Creation) test

This test measures the number of times a process can have a child thread and quit immediately. The new process creates process blocking and memory usage, so the test program uses the memory bandwidth directly. This test is used to create a large number of typical operating system processes.

Shell Scripts Test

The shell script test is used to measure the number of times a process can start and stop shell scripts within one minute. It usually tests the common copying of 1, 2, 3, 4, and 8 shell scripts, shell scripts are a set of scripts used to convert data files.

System Call Overhead (System Call consumption) test

This test measures the consumption of incoming and outgoing system kernels, for example, the consumption of system calls. The program simply repeats the getpid call (the id of the called process is returned ). The consumed metric is the execution time when the call enters and leaves the kernel.

Graphical Tests (graph) test

Consists of the "ubgears" program to test very coarse 2D and 3D graphics performance, especially 3D testing is very limited. The test result is closely related to the hardware and the appropriate driver of the system.

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 you do not need to test the image, comment out the line of the Makefile file.

# 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,200 7 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.67 GHz (5331.8 bogomips)
X86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization alization
08:24:54 up 1 day, 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

This article permanently updates the link address: