Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Slow local HAProxy performance on proxmox VM

    Scheduled Pinned Locked Moved Virtualization
    2 Posts 1 Posters 782 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      robca402
      last edited by

      For a long time I've run pfsense on bare metal and it's been flawless routing my 1Gbps internet connection, and all my devices/services. On this bare metal setup when I accessed my nextcloud instance locally via haproxy (https://cloud.mydomain.com) I would get full 1Gbps speeds (>80MBps). After virtualising pfsense and restoring the config backup, I am always limited to 30MBps when going through haproxy, no matter what I try. If I access it via local IP I get >80MBps, but going via haproxy

      I've allocated 4 cores, 4gb ram to the pfsense VM. I followed netgate documentation for installing pfsense on proxmox, including disabling hardware checksum offload. Config otherwise is identical to the old setup. Also to note I use pureNAT with both 1:1 NAT reflection and automatic outbound NAT for reflection on. Though I've experimented turning these off/on to no effect.

      It's important to note I have no other issues whatsoever with my VM, I get full gigabit internet speeds to all devices, can move things around over the network at full speeds. The only issue I have is poor performance accessing my nextcloud via https haproxy.

      My only thought possibly is needing to change an offloading setting on physical NIC on the proxmox host using ethtool? But I don't know.

      Any help would be hugely appreciated as I regularly download large files from my nextcloud instance. Sorry if I have left out any critical information, I can provide anything you need.

      R 1 Reply Last reply Reply Quote 0
      • R
        robca402 @robca402
        last edited by

        @robca402 If anyone ever see this, my problem was that I needed to toggle the AES CPU flag on in proxmox

        1 Reply Last reply Reply Quote 1
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.