Sorry, you need to enable JavaScript to visit this website.

Linux Kernel Performance

Linux development evolves rapidly. The performance and scalability of the OS kernel has been a key part of its success. However, discussions have appeared on LKML (Linux Kernel Mailing List) regarding large performance regression between kernel versions. These discussions underscore the need for a systematic and disciplined way to characterize, improve, and test Linux kernel performance. Our goal is to work with the Linux community to further enhance the Linux kernel with consistent performance increases (avoiding degradations) across releases. The information available on this site gives community members better information about what 0-Day and LKP (Linux Kernel Performance) are doing to preserve performance integrity of the kernel.

0-Day CI Linux Kernel Performance Report (v5.3)

BY Rong Chen ON Oct 16, 2019

 

  1. Introduction

0-Day CI is an automated Linux kernel test service that provides comprehensive test coverage of the Linux kernel. It covers kernel build, static analysis, boot, functional, performance and power tests. This report shows the recent observations of kernel performance status on IA platform based on the test results from 0-Day CI service. It is structured in the following manner:

  • Section 2, merged regressions and improvements in v5.3 release candidates

  • Section 3, test parameter description

  • Section 4, captured regressions and improvements by shift-left testing during developers’ and maintainers’ tree during v5.3 release cycle

  • Section 5, performance comparison among different kernel releases

  • Section 6, test machine list

 

  1. Test parameters

Here are the descriptions for each parameter/field used in the tests. 

 

Classification

Name

Description

General

runtime

Run the test case within a certain time period (seconds or minutes)

 

nr_task

If it is an integer, which means the number of processes/threads (to run the workload) of this job. Default is 1.

If it is a percentage, e.g. 200% means the number of processes/threads is double of cpu number

 

nr_threads

Alias of nr_task

 

iterations

Number to repeat this job

 

test_size

Test disk size or memory size

 

set_nic_irq_affinity

Set NIC interrupt affinity

 

disable_latency_stats

Latency_stats may introduce too much noise if there are too many context switches, allow to disable it

 

transparent_hugepage

Set transparent hugepage policy (/sys/kernel/mm/transparent_hugepage)

 

boot_params:bp1_memmap

Boot parameters of memmap

 

disk:nr_pmem

number of pmem partitions used by test

 

swap:priority

Priority means the  priority of the swap device. priority is a value between -1 and 32767, the default is -1 and higher priority with higher value. 

Test Machine

model

Name of Intel processor microarchitecture

 

brand

Brand name of cpu

 

cpu_number

Number of cpu

 

memory

Size of memory


 

  1. Linux Kernel v5.3 Release Test

The v5.3 release of the Linux kernel was on Sep 15, 2019. The announcement includes a long discussion about user-space regressions — an ext4 filesystem performance improvement had caused some systems to fail booting due to a lack of entropy early after startup. "It's more that it's an instructive example of what counts as a regression, and what the whole 'no regressions' kernel rule means. The reverted commit didn't change any API's, and it didn't introduce any new bugs. But it ended up exposing another problem, and as such caused a kernel upgrade to fail for a user. So it got reverted."

Some of the more significant changes in 5.3 include scheduler utilization clamping, the pidfd_open() and clone3() system calls, bounded loop support for BPF programs, support for the 0.0.0.0/8 IPv4 address range, a new configuration option for the soon-to-be-merged realtime preemption code, and more. See the KernelNewbies 5.3 page for lots of details.

 

0-Day CI monitored the release closely to trace down the performance status on IA platform. 0-Day observed 3 regressions and 2 improvements during feature development phase for v5.3. We will share more detailed information together with correlated patches that led to the results. Note that the assessment is limited by the test coverage 0-Day has now. The list is summarized in the observation summary section.

    1. Observation Summary

0-Day CI observed 3 regressions and 2 improvements during feature development phase for v5.3, which is in the time frame from v5.3-rc1 to v5.3 release. 

Test Indicator

Report

Test Scenario

Test Machine

Development Base

Status

aim7.jobs-per-min

[LKP] [xfs] 490d451fa5: -6.3% regression

disk: 4BRD_12G

md: RAID0

fs: xfs

test: disk_src

load: 3000

cpufreq_governor: performance

lkp-skl-2sp7

v5.2-rc4


 

merged at v5.3-rc1, no response from author yet

reaim.jobs_per_min

[LKP] [x86/topology] 212bf4fdb7: 36.4% improvement

runtime: 300s

nr_task: 100%

test: custom

cpufreq_governor: performance

lkp-bdw-ex1

v5.2-rc1

merged at v5.3-rc1

reaim.jobs_per_min

[LKP] [locking/rwsem] 4f23dbc1e6: -37.0% regression

runtime: 300s

nr_task: 7000t

test: shared_memory

cpufreq_governor: performance

lkp-ivb-2ep1

v5.2-rc5

merged at v5.3-rc1, the author is checking the possibility to reduce the regression.

vm-scalability.median

[LKP] [locking/rwsem] 7d43f1ce9d: -16.5% regression

runtime: 300s

size: 8T

test: anon-w-seq-mt

cpufreq_governor: performance

lkp-csl-2ap1

v5.2-rc5

merged at v5.3-rc1, no response from author yet

will-it-scale.per_thread_ops

[LKP] [locking/rwsem] cf69482d62: 320.6% improvement

nr_task: 16

mode: thread

test: malloc1

cpufreq_governor: performance

lkp-ivb-d02

v5.2-rc5

merged at v5.3-rc1

    1. aim7.jobs-per-min

aim7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of a multiuser system. 

 

      1. scenario: disk_src test on xfs

 

Commit 490d451fa5 was reported to have -6.3% of aim7.jobs-per-min when comparing to v5.2-rc4. It was merged to mainline at v5.3-rc1.

 

Correlated commits

490d451fa5

xfs: fix inode_cluster_size rounding mayhem

branch

linus/master

report

LKP] [xfs] 490d451fa5: -6.3% regression

test scenario

disk: 4BRD_12G

md: RAID0

fs: xfs

test: disk_src

load: 3000

cpufreq_governor: performance

test machine

lkp-skl-2sp7

status

merged at v5.3-rc1, no response from author yet

 

    1. reaim.jobs_per_min

reaim updates and improves the existing Open Source AIM 7 benchmark. aim7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of a multiuser system.

    1. scenario: shared_memory test

 

 

Commit 4f23dbc1e6 was reported to have -37.0% of reaim.jobs_per_min when comparing to v5.2-rc5. It was merged to mainline at v5.3-rc1.

 

Correlated commits

4f23dbc1e6

locking/rwsem: Implement lock handoff to prevent lock starvation

branch

linux-next/master

report

[LKP] [locking/rwsem] 4f23dbc1e6: -37.0% regression

test scenario

runtime: 300s

nr_task: 7000t

test: shared_memory

cpufreq_governor: performance

test machine

lkp-ivb-2ep1

status

merged at v5.3-rc1, the author is checking the possibility tol reduce the regression.

 

  1. will-it-scale.per_thread_ops

Will-it-scale takes a test case and runs it from 1 through to n parallel copies to see if the test case will scale. It builds both process and threads based tests in order to see any differences between the two.

Scenario: thread malloc1

 

 

Commit cf69482d62 was reported to have 320.6% of will-it-scale.per_thread_ops when comparing to v5.2-rc5. It was merged to mainline at v5.3-rc1.

 

Correlated commits

cf69482d62

locking/rwsem: Enable readers spinning on writer

branch

linus/master

report

[LKP] [locking/rwsem] cf69482d62: 320.6% improvement

test scenario

nr_task: 16

mode: thread

test: malloc1

cpufreq_governor: performance

test machine

lkp-ivb-d02

status

merged at v5.3-rc1

 

  1. Shift-Left Testing

Beyond testing trees in the upstream kernel, 0-Day CI also tests developers’ and maintainers’ trees, which can catch issues earlier and reduce wider impact. We call it “shift-left” testing. During the v5.3 release cycle, 0-Day CI had reported 21 major performance regressions and 6 major improvements by doing shift-left testing. We will share more detailed information together with possible code changes that led to this result for some of these, though the assessment is limited by the test coverage we have now. The whole list is summarized at report summary section.

    1. Report Summary

0-Day CI had reported 21 performance regressions and 6 improvements by doing shift-left testing on developer and maintainer repos.

 

Test Indicator

Mail

Test Scenario

Test Machine

Status

aim7.jobs-per-min

[LKP] [btrfs] 0096420adb: 18.3% improvement

disk: 1BRD_48G

fs: btrfs

test: disk_wrt

load: 1500

cpufreq_governor: performance

lkp-csl-2ap2

merged at v5.4-rc1

aim7.jobs-per-min

[LKP] [xfs] 1aabb011bf: -17.8% regression

disk: 4BRD_12G

md: RAID0

fs: xfs

test: disk_rw

load: 3000

cpufreq_governor: performance

lkp-ivb-ep01

currently not merged, no response from author yet

aim7.jobs-per-min

[LKP] [xfs] 73a16a2894: -31.6% regression

disk: 4BRD_12G

md: RAID0

fs: xfs

test: disk_src

load: 3000 

cpufreq_governor: performance

lkp-ivb-ep01


 

currently not merged, no response from author yet

aim7.jobs-per-min

[LKP] [btrfs] cb49511328: 3.1% improvement

disk: 4BRD_12G

md: RAID1

fs: btrfs

test: sync_disk_rw 

load: 20

cpufreq_governor: performance

lkp-skl-2sp7

merged at v5.4-rc1

aim9.dir_rtns_1.ops_per_sec

[LKP] c25aa432ff: -24.5% regression

testtime: 300s test: dir_rtns_1 cpufreq_governor: performance

lkp-ivb-d03

currently not merged, The author is working on it.

aim9.dir_rtns_1.ops_per_sec

[LKP] d4f4de5e5e: -26.1% regression

testtime: 5s

est: all

cpufreq_governor: performance

lkp-ivb-d03

merged at v5.4-rc3, no response from author yet

fio.read_bw_MBps

[LKP] [mm/lru] e7d15a9f8a: -47.0% regression

disk: 2pmem

fs: ext4

runtime: 200s

nr_task: 50%

time_based: tb

rw: read

bs: 2M

ioengine: mmap

test_size: 200G

ucode: 0x5000021

cpufreq_governor: performance

lkp-csl-2sp6

currently not merged, no response from author yet

fio.write_bw_MBps

[LKP] [blk] b91f4a426e: -9.3% regression

runtime: 300s

disk: 1HDD

fs: ext4

nr_task: 100%

test_size: 128G

rw: write

bs: 4k

ioengine: sync

ucode: 0x200005e

cpufreq_governor: performance

lkp-skl-2sp8

currently not merged, no response from author yet

fsmark.files_per_sec

[LKP] [xfs] 8afc415a53: -51.6% regression

iterations: 1x

nr_threads: 1t

disk: 1BRD_48G

fs: xfs

filesize: 4M

test_size: 40G

Sync_method:

fsyncBeforeClose

cpufreq_governor: performance

lkp-ivb-ep01

currently not merged, no response from author yet

fsmark.files_per_sec

[LKP] [nfsd] 5920afa3c8: 35.8% improvement

iterations: 1x

nr_threads: 64t

disk: 1BRD_48G

fs: f2fs

fs2: nfsv4

filesize: 4M

test_size: 40G

sync_method: NoSync

cpufreq_governor: performance

lkp-ivb-ep01

merged at v5.4-rc1

hackbench.throughput

[LKP] [sched/fair] 680b57ec48: 48.0% improvement

nr_threads: 100%

mode: threads

ipc: pipe

ucode: 0xb8 

cpufreq_governor: performance

lkp-cfl-e1

currently not merged

netpipe.bigger_5M_Mbps.avg

[LKP] [tcp] 1a9914884d: -8.0% regression

test: tcp

cluster: cs-localhost

cpufreq_governor: performance

lkp-ivb-d04

merged at v5.4-rc1, no response from author yet

reaim.jobs_per_min

[LKP] ce6cd6796e: -60.5% regression

nr_task: 1600%

iterations: 4

test: new_fserver

cpufreq_governor: performance

lkp-hsw-4ex1

currently not merged, no response from author yet

reaim.jobs_per_min

[LKP] [mm/lru] 4084fff845: -49.9% regression

runtime: 300s

nr_task: 1000t

test: page_test

cpufreq_governor: performance

lkp-ivb-2ep1

currently not merged, no response from author yet

reaim.jobs_per_min

[LKP] [sched/fair] 785087b9d6: 13.2% improvement

runtime: 300s

nr_task: 100%

test: five_sec

cpufreq_governor: performance

lkp-ivb-d04

currently not merged

stress-ng.madvise.ops_per_sec

[LKP] [mm] 87eaceb3fa: -19.6% regression

nr_threads: 100%

disk: 1HDD

testtime: 1s

class: vm

ucode: 0x200005e

cpufreq_governor: performance

lkp-skl-2sp8

merged at v5.4-rc1, the author is working on it.

unixbench.score

[LKP] [sched/fair] 537c4266fa: -9.3% regression

runtime: 300s

nr_task: 1

test: shell8

cpufreq_governor: performance

lkp-skl-fpga01

currently not merged, no response from author yet

unixbench.score

[LKP] [sched/fair] f2500eb7cb: -10.6% regression

runtime: 300s

nr_task: 1

test: shell8

cpufreq_governor: performance

lkp-skl-fpga01

currently not merged, no response from author yet

vm-scalability.median

[LKP] [locking/rwsem] 7813430057: -42.5% regression

runtime: 300s

test: small-allocs-mt

cpufreq_governor: performance

lkp-bdw-ep4

merged at v5.3-rc2, no response from author yet

vm-scalability.median

[LKP] [vfs] 8bb3c61baf: -23.7% regression

runtime: 300s

size: 16G

test: shm-pread-rand

cpufreq_governor: performance

lkp-bdw-ep4

currently not merged, no response from author yet

vm-scalability.median

[LKP] [mm/lruvec] 3145e78472: -18.4% regression

runtime: 300s

test: lru-file-readtwice

cpufreq_governor: performance

lkp-skl-fpga01

currently not merged, no response from author yet

vm-scalability.median

[LKP] [perf/core] a449d92620: -6.8% regression

runtime: 300s

size: 8T

test: anon-w-seq

cpufreq_governor: performance

lkp-ivb-d02

currently not merged, no response from author yet

will-it-scale.per_process_ops

[LKP] [cpuidle] 259231a045: -12.6% regression

nr_task: 100%

mode: process

test: mmap1

cpufreq_governor: performance

lkp-knm01

merged at v5.4-rc1, no response from author yet

will-it-scale.per_process_ops

[LKP] [mm] 0f5b256b2c: -1.2% regression

nr_task: 100%

mode: process

test: page_fault2

cpufreq_governor: performance

lkp-bdw-ep6

currently not merged, no response from author yet

will-it-scale.per_process_ops

[LKP] [mm] e0e7df8d5b: -7.3% regression

nr_task: 100%

mode: process

test: open1 cpufreq_governor: performance

lkp-csl-2ap4

currently not merged, no response from author yet

will-it-scale.per_process_ops

[LKP] [futex] 78f7688d1f: -2.2% regression

nr_task: 16

mode: process

test: futex4 cpufreq_governor: performance

lkp-csl-2ap2

currently not merged, no response from author yet

will-it-scale.per_process_ops

[LKP] [mm/page_alloc.c] 550521d945: 13.4% improvement

nr_task: 100%

mode: process

test: page_fault2

ucode: 0x200005e cpufreq_governor: performance

lkp-skl-2sp8

currently not merged

    1. aim7.jobs-per-min

aim7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of a multiuser system. 

 

      1. scenario: disk_src test on xfs

 

Commit 73a16a2894 was reported to have -31.6% regression of aim7.jobs-per-min when comparing to v5.3-rc7.

 

Correlated commits

73a16a2894

xfs: parallelize inode inactivation

branch

djwong-wtf/djwong-wtf

report

[LKP] [xfs] 73a16a2894: -31.6% regression

test scenario

disk: 4BRD_12G

md: RAID0

fs: xfs

test: disk_src

load: 3000 

cpufreq_governor: performance

test machine

lkp-ivb-ep01

status

Currently not merged, no response from author yet

 

    1. hackbench.throughput

Hackbench is both a benchmark and a stress test for the Linux kernel scheduler. It's main job is to create a specified number of pairs of schedulable entities (either  threads or traditional processes) which communicate via either sockets or pipes and time how long it takes for each pair to send data back and forth.

      1. scenario: threads pipe

 

Commit 680b57ec48 was reported to have 48.0% improvement of hackbench.throughput when comparing to v5.3-rc2.

 

Correlated commits

680b57ec48

sched/fair: use load instead of runnable load in wakeup path

branch

vincent.guittot/sched/pelt

report

[LKP] [sched/fair] 680b57ec48: 48.0% improvement

test scenario

nr_threads: 100%

mode: threads

ipc: pipe

ucode: 0xb8 

cpufreq_governor: performance

test machine

lkp-cfl-e1

status

currently not merged

 

    1. will-it-scale.per_process_ops

Will-it-scale takes a test case and runs it from 1 through to n parallel copies to see if the test case will scale. It builds both process and threads based tests in order to see any differences between the two.

Scenario: process mmap1

 

 

Commit 259231a045 was reported to have -12.6% regression of will-it-scale.per_process_ops when comparing to v5.3-rc2. It was merged to mainline at v5.4-rc1.

 

Correlated commits

259231a045

cpuidle: add poll_limit_ns to cpuidle_device structure

branch

linux-next/master

report

[LKP] [cpuidle] 259231a045: -12.6% regression

test scenario

nr_task: 100%

mode: process

test: mmap1

cpufreq_governor: performance

test machine

lkp-knm01

status

merged at v5.4-rc1, no response from author yet

 

  1. Latest Release Performance Comparing

 

This session gives some information about the performance difference among different kernel releases, especially between v5.3 and v5.2. There are 50+ performance benchmarks running in 0-Day CI, and we selected 9 benchmarks which historically showed the most regressions/improvements reported by 0-Day CI. Some typical configuration/parameters are used to run the test. For some of the regressions from the comparing, 0-Day did not successfully bisect it thus no related report sent out during the release development period, but it is still worth to check. The root cause to cause the regressions won’t be covered in this session. 

 

In the following figures, the value on the Y-axis is the relative performance number. We used the v5.2 data as the base (performance number is 100).

    1. test suite: vm-scalability

vm-scalability exercises functions and regions of the mm subsystem of the Linux kernel. Below 4 tests show the typical test results. 

 

vm-scalability Test 1

vm-scalability Test 2

vm-scalability Test 3

vm-scalability Test 4

 

Here are the test configuration and performance test summary for above tests:                                                                                                                                                                                                           

 

vm-scalability Test 1 

vm-scalability Test 2 

vm-scalability Test 3

vm-scalability Test 4

test machine

model: Haswell-EX

brand: Intel(R) Xeon(R) CPU E7-8890 v3 @ 2.50GHz

cpu_number: 144

memory: 512G

model: Haswell-EX

brand: Intel(R) Xeon(R) CPU E7-8890 v3 @ 2.50GHz

cpu_number: 144

memory: 512G

model: Haswell-EX

brand: Intel(R) Xeon(R) CPU E7-8890 v3 @ 2.50GHz

cpu_number: 144

memory: 512G

model: Ivy Bridge

brand: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz

cpu_number: 4

memory: 8G

runtime

300s

300s

No requirement

300s

nr_task

No requirement

No requirement

32

No requirement

size

1T

512G

No requirement

No requirement

boot_params

No requirement

No requirement

bp1_memmap: 120G!4G

bp2_memmap: 120G!130G

bp3_memmap: 120G!258G

bp4_memmap: 120G!386G

No requirement

disk

No requirement

No requirement

ssd_partitions: 

nr_pmem: 4

No requirement

swap

No requirement

No requirement

priority: 1

No requirement

transparent_hugepage

No requirement

No requirement

thp_enabled: never

thp_defrag: never

No requirement

vm-scalability test parameter

test case: lru-shm

test case: anon-w-rand-mt


 

test case: swap-w-seq

test case: small-allocs-mt

performance summary

vm-scalability.throughput on kernel v5.3 has -28.83% regression when comparing to v5.2

vm-scalability.throughput on kernel v5.3 has -4.49% regression when comparing to v5.2

vm-scalability.throughput on kernel v5.3 has 4.91% improvement when comparing to v5.2

vm-scalability.throughput on kernel v5.3 has 33.96% improvement when comparing to v5.2

 

    1. test suite: will-it-scale

Will-it-scale takes a test case and runs it from 1 through to n parallel copies to see if the test case will scale. It builds both process and threads based tests in order to see any differences between the two.

 

will-it-scale  Test 1

Will-it-scale Test 2

will-it-scale  Test 3

will-it-scale  Test 4

 

Here are the parameters and performance test summary for above tests:                                                                                                                                                                                                                          

 

will-it-scale Test 1 

will-it-scale Test 2 

will-it-scale Test 3 

will-it-scale Test 4 

test machine

model: Haswell-EP

brand: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz

cpu_number: 72

memory: 128G

model: Broadwell-EX

brand: Intel(R) Xeon(R) CPU E7-8890 v4 @ 2.20GHz

cpu_number: 160

memory: 256G

model: Ivy Bridge

brand: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz

cpu_number: 4

memory: 8G

model: Ivy Bridge

brand: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz

cpu_number: 4

memory: 4G

nr_task

100%

No requirement

16

No requirement

will-it-scale test parameter

mode: thread

test: malloc1

test: unlink1


 

mode: thread

test: writeseek2

test: malloc1

summary

will-it-scale.per_thread_ops on kernel v5.3 has -87.95% regression when comparing to v5.2

will-it-scale.scalability on kernel v5.3 has -31.18% regression when comparing to v5.2

will-it-scale.per_thread_ops on kernel v5.3 has -8.18% regression when comparing to v5.2

will-it-scale.per_thread_ops on kernel v5.3 has 23.61% improvement when comparing to v5.2

 

    1. test suite: unixbench

UnixBench is a system benchmark to provide a basic indicator of the performance of a Unix-like system.

 

Unixbench Test 1

 

 

Here are the test configuration and performance test summary for above tests:                                                                                                                                                                                                           

 

Unixbench Test 1 

test machine

model: Coffee Lake

brand: Intel(R) Xeon(R) E-2278G CPU @ 3.40GHz

cpu_number: 16

memory: 32G

disable_latency_stats

1

runtime

300s

nr_task

30%

unixbench test parameter

testcase: fstime


 

performance summary

unixbench.score on kernel v5.3 has 4.69% improvement when comparing to v5.2

 

    1. test suite: reaim

reaim updates and improves the existing Open Source AIM 7 benchmark. aim7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of a multiuser system.

 

reaim Test 1                             

reaim Test 2


 

Here are the test configuration and performance test summary for above tests:                                                                                                                                                                                                                      

 

reaim Test 1 

reaim Test 2 

test machine

model: Ivy Bridge-EP

brand: Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz

cpu_number: 48

memory: 64G

model: Ivy Bridge-EP

brand: Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz

cpu_number: 48

memory: 64G

runtime

300s

300s

nr_task

300t

1000t

reaim test parameter

test: disk_wrt

nr_job: 5000t

test: pipe_cpy

performance  summary

reaim.jobs_per_min on kernel v5.3 has -66.43% regression when comparing to v5.2

reaim.jobs_per_min on kernel v5.3 has -3.8% regression when comparing to v5.2

                                                                                                                                                                                                     

    1. test suite: pigz

pigz, which stands for Parallel Implementation of GZip, is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data.

pigz Test 1 


 

 

Here are the test configuration and performance test summary for above tests:          

 

 

pigz Test 1

test machine

model: Ivy Bridge

brand: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz

cpu_number: 4

memory: 4G

nr_threads

100%

pigz Test parameter

blocksize: 512K

performance  summary

pigz.throughput on kernel v5.3 is almost the same as that in v5.2

            

  1. test suite: netperf

Netperf is a benchmark that can be used to measure the performance of many different types of networking. It provides tests for both unidirectional throughput, and end-to-end latency.

 

netperf Test 1

 

Here are the test configuration and performance test summary for above tests:                                                                                                                                                                                                                          

 

netperf Test 1 

test machine

model: Coffee Lake

brand: Intel(R) Xeon(R) E-2278G CPU @ 3.40GHz

cpu_number: 16

memory: 32G

disable_latency_stats

1

set_nic_irq_affinity

1

runtime

300s

nr_threads

1

ip

ipv4

netperf test parameter

send_size: 10K

test case: SCTP_STREAM_MANY

performance  summary

netperf.Throughput_Mbps on kernel v5.3 is almost the same as that in v5.2

 

    1. test suite: hackbench

Hackbench is both a benchmark and a stress test for the Linux kernel scheduler. It's  main job is to create a specified number of pairs of schedulable entities (either threads or traditional processes) which communicate via either sockets or pipes and time how long  it takes for each pair to send data back and forth.

hackbench Test 1


 
 

Here are the test configuration and performance test summary for above tests:                                                                                                                                                                                                           

 

Hackbench Test 1 

test machine

model: Haswell-EP

brand: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz

cpu_number: 72

memory: 128G

disable_latency_stats

1

runtime

300s

nr_task

50%

unixbench test parameter

iterations: 12

mode: process

ipc: pipe

performance summary

hackbench.throughput on kernel v5.3 is almost the same as that in v5.2

            

    1. test suite: fio

Fio was originally written to save me the hassle of writing special test case programs when I wanted to test a specific workload, either for performance reasons or to find/reproduce a bug.

fio Test 1 

  

 

Here are the test configuration and performance test summary for above tests:                                                                                                                                                                                                                          

 

fio Test 1 

test machine

model: Cascade Lake

brand: Intel(R) Xeon(R) CPU @ 2.20GHz

cpu_number: 192

memory: 192G

runtime

300s

file system

btrfs

disk

1SSD

nr_task

100%

fio test parameter

fio-setup-basic:

  rw: randwrite

  bs: 4M

  ioengine: sync

performance  summary

fio.write_bw_MBps on kernel v5.3 is almost the same as that in v5.2

 

    1. test suite: ebizzy

ebizzy is designed to generate a workload resembling common web application server workloads. It is highly threaded, has a large in-memory working set, and allocates and deallocates memory frequently.

ebizzy Test 1

 

 

Here are the test configuration and performance test summary for above test:                                                                                                                                                                                                                          

 

ebizzy Test 1

test machine

model: Broadwell-EX

brand: Intel(R) Xeon(R) CPU E7-8890 v4 @ 2.20GHz

cpu_number: 160

memory: 256G

nr_threads

200%

iterations

100x

ebizzy test parameter

duration: 10s

performance  summary

ebizzy.throughput on kernel v5.3 has -6.81% regression when comparing to v5.2


 

  1. Test Machines

    1. IVB Desktop

model

Ivy Bridge

brand

Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz

cpu number

8

memory

16G

 

model

Ivy Bridge

brand

Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz

cpu number

4

memory

8G

 

    1. SKL SP

model

Skylake

brand

Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz

cpu number

80

memory

64G

 

    1. BDW EP

model

Broadwell-EP

brand

Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz

cpu number

88

memory

128G

 

    1. HSW EP

model

Haswell-EP

brand

Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz

cpu number

72

memory

128G

 

    1. IVB EP

model

Ivy Bridge-EP

brand

Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz

cpu number

40

memory

384G

 

model

Ivytown Ivy Bridge-EP

brand

Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz

cpu number

48

memory

64G

 

    1. HSX EX

model

Brickland Haswell-EX

brand

Intel(R) Xeon(R) CPU E7-8890 v3 @ 2.50GHz

cpu number

144

memory

512G