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

Feedback

Your feedback is important to keep improving our website and offer you a more reliable experience.

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.0)

BY Rong Chen ON Mar 15, 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.0 release candidates

  • Section 3, test parameter description

  • Section 4, captured regressions and improvements by shift-left testing during developers’ and maintainers’ tree during v5.0 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 periods (seconds or minutes)

 

nr_task

If it is an integer, 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.0 Test

The v5.0 release of the Linux kernel was on March 3, 2019. Some of the headline features in 5.0 include  the energy-aware scheduling patch set, a bunch of year-2038 work that comes close to completing the core-kernel transition, zero-copy networking for UDP traffic, the Adiantum encryption algorithm, the seccomp trap to user space mechanism, and, of course, lots of new drivers and fixes. See the KernelNewbies 5.0 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 4 improvements during feature development phase for v5.0. 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 4 improvements during feature development phase for v5.0, which is in the time frame from v5.0-rc1 to v5.0 release.

Test Indicator

Report

Test Scenario

Test Machine

Development Base

Status

aim7.jobs-per-min

[LKP] [f2fs] 089842de57: 15.4% improvement

disk: 4BRD_12G

md: RAID1

fs: f2fs

test: disk_rw

load: 3000

cpufreq_governor: performance


 

lkp-ivb-ep01

v4.20-rc4


 

merged at v5.0-rc1

fio.write_bw_MBps

[LKP] [btrfs] 64403612b7: 5.3% improvement

disk: 2pmem

fs: btrfs

runtime: 200s

nr_task: 50%

time_based: tb

rw: randwrite

bs: 4k

ioengine: mmap

test_size: 100G

cpufreq_governor: performance

lkp-hsw-ep6

v4.20-rc7

merged at v5.0-rc1

fio.write_bw_MBps

[LKP] [btrfs] 302167c50b: -12.4% regression

runtime: 300s

nr_task: 8t

disk: 1SSD

fs: btrfs

rw: randwrite

bs: 4k

ioengine: sync

test_size: 400g

cpufreq_governor: performance

lkp-bdw-ep3b

v4.20-rc7

merged at v5.0-rc5,no response from author yet

fsmark.files_per_sec

[LKP] [ext4] fde872682e: -38.0% regression

iterations: 4

disk: 1SSD

nr_threads: 4

fs: ext4

fs2: nfsv4

filesize: 9B

test_size: 10G

sync_method: fsyncBeforeClose

nr_directories: 16d

nr_files_per_directory: 256fpd

cpufreq_governor: performance

lkp-hsw-ep4

v4.20-rc4

merged at v5.0-rc1, this is a correctness issue and maybe needs 3 months or so to fix it.


 

stress-ng.eventfd.ops

[LKP] [fs/locks] fd7732e033: 21.9% improvement

nr_threads: 100%

disk: 1HDD

testtime: 1s

class: filesystem

ucode: 0xb00002e

cpufreq_governor: performance

lkp-bdw-ep3

v4.20-rc2

merged at v5.0-rc1


 

vm-scalability.throughput

[LKP] [mm, fault_around] e0975b2aae: 7.2% improvement

runtime: 300s

size: 2T

test: shm-pread-seq

cpufreq_governor: performance

lkp-hsx04

v4.20

merged at v5.0-rc1

will-it-scale.per_process_ops

[LKP] [PM] 8234f6734c: -3.6% regression

rnr_task: 100%

mode: process

test: poll2

cpufreq_governor: performance

lkp-skl-fpga01

v4.20-rc7


 

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


 
  1. fio.write_bw_MBps

Fio is a tool that will spawn a number of threads or processes doing a particular type of I/O action as specified by the user.

scenario: randwrite on btrfs

 

Commit 302167c50b was reported to have of fio.write_bw_MBps when comparing to v4.20-rc7." It was merged to mainline at v5.0-rc5."

 

Correlated commits

302167c50b

btrfs: don't end the transaction for delayed refs in throttle

branch

linux-next/pending-fixes

report

[LKP] [btrfs] 302167c50b: fio.write_bw_MBps -12.4% regression

Test Scenario

runtime: 300s
nr_task: 8t
disk: 1SSD
fs: btrfs
rw: randwrite
bs: 4k
ioengine: sync
test_size: 400g

Test Machine

lkp-bdw-ep3b

status

merged at v5.0-rc5, no response from author yet

 

  1. fsmark.files_per_sec

The fsmark is a file system benchmark to test synchronous write workloads, for example, mail servers workload.

scenario: fsyncBeforeClose on ext4

 

Commit fde872682e was reported to have of fsmark.files_per_sec when comparing to v4.20-rc4." It was merged to mainline at v5.0-rc1."

 

Correlated commits

fde872682e

ext4: force inode writes when nfsd calls commit_metadata()

branch

linus/master

report

[LKP] [ext4] fde872682e: fsmark.files_per_sec -38.0% regression

Test Scenario

iterations: 4

disk: 1SSD

nr_threads: 4

fs: ext4

fs2: nfsv4

filesize: 9B

test_size: 10G

sync_method: fsyncBeforeClose

nr_directories: 16d

nr_files_per_directory: 256fpd

Test Machine

lkp-hsw-ep4

status

merged at v5.0-rc1, this is a correctness issue and maybe needs 3 months or so to fix it.

 

  1. vm-scalability.throughput

vm-scalability exercises functions and regions of the mm subsystem of the Linux kernel. We tested on multiple machines such as HSW EP server, during which we reported improvement on one test scenario.

Scenario: shm-pread-seq test

 

Commit e0975b2aae was reported to have 7.2% improvement of vm-scalability.throughput when comparing to v4.20." It was merged to mainline at v5.0-rc1."

 

Correlated commits

e0975b2aae

mm, fault_around: do not take a reference to a locked page

branch

linus/master

report

[LKP] [mm, fault_around] e0975b2aae: vm-scalability.throughput 7.2% improvement

Test Scenario

runtime: 300s

size: 2T

test: shm-pread-seq

Test Machine

lkp-hsx04

status

merged at v5.0-rc1

 

  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 poll2

 

Commit 8234f6734c was reported to have -3.6% regression of will-it-scale.per_process_ops when comparing to v4.20-rc7." It was merged to mainline at v5.0-rc1."

 

Correlated commits

8234f6734c

PM-runtime: Switch autosuspend over to using hrtimers

branch

linus/master

report

[LKP] [PM] 8234f6734c: will-it-scale.per_process_ops -3.6% regression

Test Scenario

rnr_task: 100%

mode: process

test: poll2

Test Machine

lkp-skl-fpga01

status

merged at v5.0-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 v4.20 release cycle, 0-Day CI had reported 15 major performance regressions and 4 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 9 performance regressions and 4 improvements by doing shift-left testing on developer and maintainer repos.

 

Test Indicator

Mail

Test Scenario

Test Machine

Status

aim7.jobs-per-min

[LKP] [xfs] 0e314dbf1a: -36.2% 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] [xfs] 5f08fede91: -7.1% regression

disk: 4BRD_12G

md: RAID1

fs: xfs

test: disk_wrt

load: 3000

cpufreq_governor: performance

lkp-ivb-ep01

Currently not merged, no response from author yet

aim7.jobs-per-min

[LKP] [xfs] ea3e90ae01: -23.5% regression

disk: 1BRD_48G

fs: xfs

test: disk_wrt

load: 3000

cpufreq_governor: performance

lkp-ivb-ep01

Currently not merged, no response from author yet

aim7.jobs-per-min

[LKP] [xfs] 4ff1f5b3d9: -30.4% regression

disk: 1BRD_48G

fs: xfs

test: disk_src

load: 3000

cpufreq_governor: performance

lkp-ivb-ep01

Currently not merged, no response from author yet

netperf.Throughput_Mbps

[LKP] [net] 62fd64b7f1: -97.0% regression

ip: ipv4

runtime: 900s

nr_threads: 1

cluster: cs-localhost

test: TCP_STREAM

cpufreq_governor: performance

lkp-bdw-ex2

Currently not merged, no response from author yet

pigz.throughput

[LKP] [mm/page_alloc.c] 148c6673c9: 2.7% improvement

nr_threads: 100%

blocksize: 128K

cpufreq_governor: performance

lkp-bdw-ep2

Currently not merged, no response from author yet

reaim.jobs_per_min

[LKP] [/proc/stat] 3047027b34: -4.8% regression

runtime: 300s

nr_task: 5000

test: shared_memory

cpufreq_governor: performance

lkp-hsw-ep5

Currently not merged, the sysctl has been dropped

reaim.jobs_per_min

[LKP] [NFS] 46c7f523fc: -5.7% regression

runtime: 300s

nr_task: 5000

test: shared_memory

cpufreq_governor: performance

lkp-hsw-ep5

Currently not merged, no response from author yet

stress-ng.numa.ops_per_sec

[LKP] [mm/gup] cdaa813278: 4671.0% improvement

nr_threads: 50%

disk: 1HDD

testtime: 5s

class: memory

cpufreq_governor: performance

lkp-bdw-ep3

Currently not merged, no response from author yet

vm-scalability.free_time

[LKP] [mm/page_alloc.c] 148c6673c9: 102.6% regression

runtime: 300s

test: lru-file-mmap-read

cpufreq_governor: performance

lkp-bdw-ep2

Currently not merged, no response from author yet

vm-scalability.median

[LKP] 2d32f12eef: -3.5% regression

runtime: 300s

size: 8T

test: anon-wx-seq-mt

cpufreq_governor: performance

lkp-skl-fpga01

Currently not merged, the author is working on it

vm-scalability.throughput

[LKP] [mm, fault_around] e0975b2aae: 7.2% improvement

runtime: 300s

size: 2T

test: shm-pread-seq

cpufreq_governor: performance

lkp-hsx04

merged at v5.0-rc1

will-it-scale.per_process_ops

[LKP] [mm/gup] e7ae097b0b: -5.0% regression

nr_task: 100%

mode: process

test: futex1

cpufreq_governor: performance

lkp-skl-4sp1

Currently not merged, no response from author yet

will-it-scale.per_thread_ops

[LKP] [locking/rwsem] 8181789168: 174.4% improvement

nr_task: 100%

mode: thread

test: brk1

cpufreq_governor: performance

lkp-ivb-d01

Currently not merged, no response from author yet

aim7.jobs-per-min

[LKP] [xfs] 0e314dbf1a: -36.2% 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

  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 0e314dbf1a was reported to have of aim7.jobs-per-min when comparing to v5.0-rc3."

 

Correlated commits

0e314dbf1a

xfs: parallelize inode inactivation

branch

djwong-xfs/deferred-inactivation

report

[LKP] [xfs] 0e314dbf1a: aim7.jobs-per-min -36.2% regression

Test Scenario

disk: 4BRD_12G

md: RAID0

fs: xfs

test: disk_src

load: 3000

Test Machine

lkp-ivb-ep01

status

Not merged at v5.0, no response from author yet

  1. netperf.Throughput_Mbps

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.

  1. scenario: TCP_STREAM test on localhost

 

Commit 62fd64b7f1 was reported to have -97.0% regression of netperf.Throughput_Mbps when comparing to v5.0-rc2."

 

Correlated commits

62fd64b7f1

net: Make softirq vector masking finegrained on release_sock()

branch

dynticks/softirq/soft-interruptible-v2-0day

report

[LKP] [net] 62fd64b7f1: netperf.Throughput_Mbps -97.0% regression

Test Scenario

ip: ipv4

runtime: 900s

nr_threads: 1

cluster: cs-localhost

test: TCP_STREAM

Test Machine

lkp-bdw-ex2

status

Not merged at v5.0, no response from author yet

 

  1. reaim.jobs_per_min

Reaim is an updated and improved version of AIM 7 benchmark. It forks many processes called tasks.

scenario: shared_memory test

Commit 46c7f523fc was reported to have -5.7% of reaim.jobs_per_min when comparing to v5.0-rc4."

 

Correlated commits

46c7f523fc

NFS: Add trace events to report non-zero NFS status codes

branch

cel/nfs-for-5.1

report

[LKP] [NFS] 46c7f523fc: reaim.jobs_per_min -5.7% regression

Test Scenario

runtime: 300s

nr_task: 5000

test: shared_memory

Test Machine

lkp-hsw-ep5

status

Not merged at v5.0, no response from author yet

 

  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 futex1

Commit e7ae097b0b was reported to have -5.0% regression of will-it-scale.per_process_ops when comparing to v5.0-rc4."

 

Correlated commits

e7ae097b0b

mm/gup: /proc/vmstat support for get/put user pages

branch

linux-review/john-hubbard-gmail-com/RFC-v2-mm-gup-dma-tracking/20190205-001101

report

[LKP] [mm/gup] e7ae097b0b: will-it-scale.per_process_ops -5.0% regression

Test Scenario

nr_task: 100%

mode: process

test: futex1

Test Machine

lkp-skl-4sp1

status

Not merged at v5.0, 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.0 and v4.20. 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.  

 

In the following figures, the value on the Y-axis is the relative performance number. We used the v4.20 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

 

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

 

vm-scalability Test 1

vm-scalability Test 2

Test machine

model: Haswell-EP
brand: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
cpu_number: 72
memory: 256G

model: Skylake
brand: Intel(R) Xeon(R) Gold 6148F CPU @ 2.40GHz
cpu_number: 40
memory: 64G

runtime

300s

300s

test_size

8T

No requirement

vm-scalability Test parameter

test case: anon-w-seq-hugetlb

test case: anon-rx-seq-mt

Performance Summary

vm-scalability.throughput on kernel v5.0 has -9.28% regression when comparing to v4.20

vm-scalability.throughput on kernel v5.0 almost the same with v4.20

 

  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


 

 

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

 

will-it-scale Test 1

Test machine

model: Skylake

brand: Genuine Intel(R) CPU 0000%@

cpu_number: 104

memory: 192G

nr_task

100%

will-it-scale Test parameter

mode: process

test case: poll2

Summary

will-it-scale.per_process_ops on kernel v5.0 has -2.1% regression when comparing to v4.20

 

  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: Broadwell-DE

brand: Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz

cpu_number: 16

memory: 8G

runtime

300

nr_task

1

unixbench Test parameter

test case: shell8

Performance Summary

unixbench.score on kernel v5.0 has -0.4% regression when comparing to v4.20

 

  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: Haswell-EP

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

cpu_number: 72

memory: 256G

model: Haswell-EP

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

cpu_number: 72

memory: 256G

runtime

300s

300s

nr_task

5000

600

reaim Test parameter

test case: shared_memory

test case: creat_clo

Performance  Summary

reaim.jobs_per_min on kernel v5.0 has -3.72% regression when comparing to v4.20

reaim.jobs_per_min on kernel v5.0 has 10.4% improvement when comparing to v4.20

 

  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: Broadwell-EP
brand: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
cpu_number: 88
memory: 128G

nr_threads

100%

pigz Test parameter

blocksize: 512K

Performance  Summary

pigz.throughput on kernel v5.0 has -0.38% regression when comparing to v4.20

           

  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

netperf Test 2



 

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

 

netperf Test 1

netperf Test 2

Test machine

model: Broadwell-EX

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

cpu_number: 160

memory: 256G

model: Broadwell-EX

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

cpu_number: 160

memory: 256G

disable_latency_stats

1

1

set_nic_irq_affinity

1

1

runtime

300s

900s

nr_threads

1

1

ip

ipv4

ipv4

netperf Test parameter

test case: UDP_STREAM

test case: TCP_STREAM

Performance  Summary

netperf.Throughput_Mbps on kernel v5.0 has 5.58% improvement when comparing to v4.20

netperf.Throughput_Mbps on kernel v5.0 has 10.89% improvement when comparing to v4.20

 

  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


 

hackbench Test 2


 

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

 

hackbench Test 1

hackbench Test 2

Test machine

model: Haswell-EP

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

cpu_number: 72

memory: 128G

model: Haswell-EP

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

cpu_number: 72

memory: 128G

disable_latency_stats

1

1

nr_threads

1600%

50%

hackbench Test parameter

iterations: 18

mode: threads

ipc: pipe

iterations: 12

mode: process

ipc: socket

Performance  Summary

hackbench.throughput on kernel v5.0 has -6.72% regression when comparing to v4.20

hackbench.throughput on kernel v5.0 has 10.66% improvement when comparing to v4.20

 

  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

 

fio Test 2

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

 

fio Test 1

fio Test 2

Test machine

model: Broadwell-EP
brand: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
cpu_number: 88
memory: 64G

model: Ivy Bridge-EP

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

cpu_number: 40

memory: 384G

disk

1SSD

1HDD

runtime

300s

300s

file system

btrfs

btrfs

test_size

No requirement

128G

nr_task

8t

100%

fio Test parameter

fio-setup-basic:

 rw: randwrite

 bs: 4k

 ioengine: sync

 test_size: 400g

fio-setup-basic:

 rw: randwrite

 bs: 4k

 ioengine: sync

Performance  Summary

fio.write_bw_MBps on kernel v5.0 has -13.39% regression when comparing to v4.20

fio.write_bw_MBps on kernel v5.0 has 5.26% improvement when comparing to v4.20

 

  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.0 almost the same with v4.20

 

  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 Desktop

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