Hello again everyone. I am sharing one last performance test I performed tonight.
PVE
Power Edge R815 with 250GB RAM and 4 sockets of 16 colors each, fiber optic adapter connected to a storage Infortrend with SSD.
VM
Windows 2008 R2 Eth with 50GB memory and socket 3 with 15 colors each, the server receives an average of 110 connections and configured with best practices https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices
Proxmox made the upgrade to the 4.2.3.2 kernel and restart the server after we started the VM, very fast to start, however when users began to connect the server was slow getting to lose packets on the network and hang.
Then returned to 3.19.8.1 kernel version in which features stability and great performance.
Note. When down the size of memory for up to 5 GB VM normally works well quickly, however when you increase the memory to 50GB the same lock.
Below is my current setup.
pve-manager: 4.0-57 (running version: 4.0-57 / cc7c2b53)
pve-kernel-3.19.8-1-pve: 3.19.8-3
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-24
qemu-server: 4.0-35
pve-firmware: 1.1-7
libpve-common-perl: 4.0-36
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-29
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
qemu-kvm-pve: 2.4-12
pve-container: 1.0-21
pve-firewall: 2.0-13
pve-ha-manager: 1.0-13
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2 + deb8u1
lxc-pve: 1.1.4-3
lxcfs: 0.10 pve2-
cgmanager: 00:39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6 ~ jessie
If anyone has any information regarding the difference between the two kernel that directly impacts the performance of Windows.
Thank you.
PVE
Power Edge R815 with 250GB RAM and 4 sockets of 16 colors each, fiber optic adapter connected to a storage Infortrend with SSD.
VM
Windows 2008 R2 Eth with 50GB memory and socket 3 with 15 colors each, the server receives an average of 110 connections and configured with best practices https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices
Proxmox made the upgrade to the 4.2.3.2 kernel and restart the server after we started the VM, very fast to start, however when users began to connect the server was slow getting to lose packets on the network and hang.
Then returned to 3.19.8.1 kernel version in which features stability and great performance.
Note. When down the size of memory for up to 5 GB VM normally works well quickly, however when you increase the memory to 50GB the same lock.
Below is my current setup.
pve-manager: 4.0-57 (running version: 4.0-57 / cc7c2b53)
pve-kernel-3.19.8-1-pve: 3.19.8-3
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-24
qemu-server: 4.0-35
pve-firmware: 1.1-7
libpve-common-perl: 4.0-36
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-29
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
qemu-kvm-pve: 2.4-12
pve-container: 1.0-21
pve-firewall: 2.0-13
pve-ha-manager: 1.0-13
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2 + deb8u1
lxc-pve: 1.1.4-3
lxcfs: 0.10 pve2-
cgmanager: 00:39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6 ~ jessie
If anyone has any information regarding the difference between the two kernel that directly impacts the performance of Windows.
Thank you.