test kernel feedback pveperf

BitRausch

Renowned Member
Mar 16, 2009
140
0
81
Muenster
hi dietmar+tom,

just testing your latest kernel and noticed that pveperf is showing different numbers:

pveperf
Code:
CPU BOGOMIPS:      42139.81
REGEX/SECOND:      1204265
HD SIZE:           39.37 GB (/dev/mapper/pve-root)
BUFFERED READS:    234.62 MB/sec
AVERAGE SEEK TIME: 14.22 ms
FSYNCS/SECOND:     98.84
DNS EXT:           1094.27 ms
DNS INT:           1.10 ms (fritz.box)

pveversion
Code:
pve-manager: 1.6-4 (pve-manager/1.6/5229)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.6-2
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.35-1-pve: 2.6.35-2
qemu-server: 1.1-19
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4

Usually FSYNCS/SECOND is above 3K on my system and BUFFERED READS above 260.

System Specs:
AMD 1055T
Adaptec 5405 writeback enabled
4 x SATA 500GB in RAID 10
8 GB RAM
NO VM's running.

I would love to give you comparison numbers but not sure how to revert back the complete changes in order to do that.

Kind regards
 
Some other numbers after installing the pve-kernel-2.6.32-4-pve

pveversion:
Code:
pve-manager: 1.6-4 (pve-manager/1.6/5229)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-21
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.32-4-pve: 2.6.32-21
pve-kernel-2.6.35-1-pve: 2.6.35-2
qemu-server: 1.1-19
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4

pveperf:
Code:
CPU BOGOMIPS:      42141.76
REGEX/SECOND:      1106365
HD SIZE:           39.37 GB (/dev/mapper/pve-root)
BUFFERED READS:    247.94 MB/sec
AVERAGE SEEK TIME: 10.38 ms
FSYNCS/SECOND:     1519.66
DNS EXT:           1102.49 ms
DNS INT:           1.09 ms (fritz.box)

kind regards
 
thanks for reporting!
 
Thx Dietmar,

here the results after applying the new kernel:

pveversion
Code:
pve-manager: 1.6-4 (pve-manager/1.6/5229)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.6-3
pve-kernel-2.6.32-4-pve: 2.6.32-21
pve-kernel-2.6.35-1-pve: 2.6.35-3
qemu-server: 1.1-19
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4

pveperf:
Code:
CPU BOGOMIPS:      42141.55
REGEX/SECOND:      1191201
HD SIZE:           39.37 GB (/dev/mapper/pve-root)
BUFFERED READS:    266.30 MB/sec
AVERAGE SEEK TIME: 12.08 ms
FSYNCS/SECOND:     1593.75
DNS EXT:           1130.10 ms
DNS INT:           1.11 ms (fritz.box)

FSYNCS/SECOND is still lower then I remember...but way better the the first version.
(I repeated the pveperf command a couple of times)

Kind regards,
 
First server:
pve-manager: 1.6-4 (pve-manager/1.6/5229)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.6-2
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.35-1-pve: 2.6.35-2
qemu-server: 1.1-19
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4
CPU BOGOMIPS: 89602.61
REGEX/SECOND: 1152007
HD SIZE: 9.84 GB (/dev/mapper/pve-root)
BUFFERED READS: 232.49 MB/sec
AVERAGE SEEK TIME: 4.60 ms
FSYNCS/SECOND: 99.49
DNS EXT: 144.90 ms

Second server:
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3
CPU BOGOMIPS: 89602.15
REGEX/SECOND: 1115224
HD SIZE: 9.84 GB (/dev/mapper/pve-root)
BUFFERED READS: 120.35 MB/sec
AVERAGE SEEK TIME: 4.39 ms
FSYNCS/SECOND: 2585.32
DNS EXT: 55.92 ms

Both servers have identical hardware (HP DL360 G6).
 
Hi l.mirzwa,

try the latest kernel (kernel-2.6.35-3) on your first server. See also the post from dietmar in this thread. That should improve FSYNCS on your first server.

kind regards
 
Hi l.mirzwa,
try the latest kernel (kernel-2.6.35-3) on your first server. See also the post from dietmar in this thread. That should improve FSYNCS on your first server.
kind regards

I run test on wrong machine, now it's the one with 2.6.35-3:
pve-manager: 1.6-4 (pve-manager/1.6/5229)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.6-3
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.35-1-pve: 2.6.35-3
qemu-server: 1.1-19
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4
CPU BOGOMIPS: 89602.35
REGEX/SECOND: 1163856
HD SIZE: 9.84 GB (/dev/mapper/pve-root)
BUFFERED READS: 127.07 MB/sec
AVERAGE SEEK TIME: 4.55 ms
FSYNCS/SECOND: 2485.65
DNS EXT: 205.96 ms
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!