Performance Issue with .NET Application on Virtual Machine

[corvdl]

Hello everyone,

I am a new Proxmox user and I'm experiencing a strange performance issue that I can't figure out.

On a clean Windows Server 2022 installation, i'm using a .NET application.
On my new server, it takes 3 to 5 minutes for this application to load.
However, all other applications like Office are reacting very fast.

I also tried a clean installation of Windows Server 2019, but I encounter the same performance issues.

On a test server - Server B - , the same application starts within 10 seconds.

Specifications of my new server (Server A):

• CPU: 80 x Intel(R) Xeon(R) Silver 4416+ (2 Sockets)
• RAM: 126 GB
• Storage: NVMe disks

Specifications of my old server (Server B):

• CPU: 32 x Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.20GHz (2 Sockets)
• RAM: 512 GB
• Storage: SSD disks

Configuration of the VM on both hosts:

• CPU: 16 processors, 2 sockets, 8 cores (x86-64-v2-aes)
• BIOS: Default
• RAM: 16 GB

---

Output of cpufreq-info on Server A:

cpufreq-info on server A gives

analyzing CPU 74:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 74
  CPUs which need to have their frequency coordinated by software: 74
  maximum transition latency: 4294.55 ms.
  hardware limits: 800 MHz - 3.90 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.90 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is .... (variate per cpu)

I checked the CPU frequency with watch -n 1 "cat /proc/cpuinfo | grep 'MHz'".

According to the CPU benchmark test, my new CPU should performs much better:CPU Benchmark Comparison

What could be a reason that this .NET application takes so long to load on the new host?

Thank you in advance for your help!

Cor

 

[leesteken]

My experience with a .NET executable taking 3 minutes to even start is a firewall that silently drops connections to the server (which makes you wait for the default timeout of three minutes) that is queried to check if the signing/certificate of the executable is revoked. Check if the application is signed and if what chain of trust is checked for its certificate, and whether the firewall blocks it silently (which is indistinguishable from a broken connection and requires a wait until timeout).

EDIT: This is not specific to Proxmox or virtualization but depends on the network setup and firewall, which might involve Proxmox.

 

[gfngfn256]

You don't provide network details for either host. What does network speed/s look like from within the VM.

 

[corvdl]

You don't provide network details for either host. What does network speed/s look like from within the VM.

The application is local installed on the vm, no network connection needed to start.
Both connected on the same switch at 1 GB

My experience with a .NET executable taking 3 minutes to even start is a firewall that silently drops connections to the server (which makes you wait for the default timeout of three minutes) that is queried to check if the signing/certificate of the executable is revoked. Check if the application is signed and if what chain of trust is checked for its certificate, and whether the firewall blocks it silently (which is indistinguishable from a broken connection and requires a wait until timeout).

EDIT: This is not specific to Proxmox or virtualization but depends on the network setup and firewall, which might involve Proxmox.

I just checked the certificate is valid an signed. Firewalls is disabled,

Strange about this is that if i do a clean install on both host exacly the same,
server A is very slow, server B is reacting normaly.
Both hosts are connected to the same switch.

 

[gfngfn256]

Both connected on the same switch at 1 GB

I'd still test / compare network speeds