Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to use unixbench to test system performance in Linux

2025-03-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/01 Report--

This article mainly introduces "how to use unixbench to test system performance in Linux". In daily operation, I believe many people have doubts about how to use unixbench in Linux to test system performance. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubt of "how to use unixbench to test system performance in Linux". Next, please follow the editor to study!

What is unixbench?

Unixbench is a benchmark suite for unix systems. The design goal of unixbench is to provide a set of basic indicators for unix-like systems, so there are many projects to test the performance of all aspects of the system. Each test has a score, and then there is a comprehensive score, which can be easily compared by the score.

Unixbench also includes some very simple 2D and 3D graphics tests.

Unixbench also supports multi-CPU system testing, the default behavior is to test twice, the first is a process test, the second is N tests, N equals the number of CPU. This is designed for the following goals:

Test the single-task performance of the system

Test the multitasking performance of the system

Test the parallel processing ability of the system

Unixbench is a system-based benchmark tool, not just a CPU memory or disk testing tool. The test results depend not only on the hardware, but also on the system, development libraries, and even compilers.

Test project

Dhrystone test

The test focuses on string processing, with no floating-point operations. This test is used to test linker compilation, code optimization, memory cache, wait state, integer data type, etc., hardware and software design will greatly affect the test results.

Whetstone test

This test project 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 language functions, sin cos sqrt exp and logs, and mathematical operations using integers and floating points. Contains array access, conditional branches, and procedure calls.

Execl Throughput (execl throughput, where execl is a very important function of unix-like systems, execl of non-office software) testing

This test tests the number of execl function calls per second. Execl is part of the exec function family and replaces the current graphics processing with new graphics processing. There are many commands that are very similar to the front-end execve () function command.

File Copy test

This test measures the transfer of file data from one file to another, using a large number of caches. Including the file read, write, copy test, the test indicator is the number of characters rewritten, read, and copied within a certain period of time (the default is 10 seconds).

Pipe Throughput (pipeline throughput) test

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

Count. There is a gap between the pipeline throughput test and the actual programming.

Pipe-based Context Switching (pipe-based contextual interaction) testing

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

Process Creation (process creation) test

This test measures the number of times a process can produce child threads and exit immediately. The new process really creates process blocking and memory footprint, so the test program uses memory bandwidth directly. This test is used for a typical large number of operating system process creation operations.

Shell Scripts test

The shell script test is used to measure the number of times a process can start and stop a shell script in a minute, usually testing a common copy of 1 shell 2, 3, 4, and 8 shell scripts are a set of scripts that convert data files.

System Call Overhead (system call consumption) test

This test measures the consumption of entering and leaving the system kernel, for example, the consumption of system calls. The program simply repeats the getpid call (returns the called process id). The indicator of consumption is the execution time for invocation to and from the kernel.

Graphical Tests (graphics) test

Made up of the "ubgears" program, testing very thick 2D and 3D graphics performance, especially 3D testing is very limited. The test results are closely related to the hardware and the appropriate driver of the system.

Unixbench installation

The code is as follows:

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 drawing, comment out this line in the Makefile file

The code is as follows:

# GRAPHIC_TESTS = defined

Running

The code is as follows:

. / Run

Test result

The code is as follows:

# # #

# # #

# # #

# # #

# # #

# # #

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.0s, 7 samples)

Double-Precision Whetstone 3880.4 MWIPS (9.0s, 7 samples)

Execl Throughput 4146.3 lps (30.0s, 2 samples)

File Copy 1024 bufsize 2000 maxblocks 1051084.3 KBps (30.0s, 2 samples)

File Copy 256 bufsize 500 maxblocks 286552.2 KBps (30.0s, 2 samples)

File Copy 4096 bufsize 8000 maxblocks 2142638.4 KBps (30.0s, 2 samples)

Pipe Throughput 1726807.0 lps (10.0s, 7 samples)

Pipe-based Context Switching 322865.5 lps (10.0s, 7 samples)

Process Creation 13662.4 lps (30.0s, 2 samples)

Shell Scripts (1 concurrent) 5955.4 lpm (60.0s, 2 samples)

Shell Scripts (8 concurrent) 713.1 lpm (60.0s, 2 samples)

System Call Overhead 2138318.1 lps (10.0s, 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

At this point, the study on "how to use unixbench in Linux to test system performance" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report