Wireguard and multithreading on FreeBSD

[dnb]

Hi all!

I have the option of choosing a virtual server with 1 or 2x5.5 GHz cores.

This server will act as a high-performance VPN server for VPN connections between 2 or 3 computers. ZFS dataset backups will be sent over the network.

Questions:

1. How much will adding a second core help me with Wireguard performance?

2. Will a second core significantly improve my system, and will Wireguard utilize the second core properly?

3. How can I see Wireguard's core usage?

Thank you!

 

[sko]

If this is halfway decent/modern hardware, don't bother about wireguard. Just use ipsec and crypto offloading (cryptodev, qat). This will easily outperform wireguard any time and ipsec is available absolutely everywhere.
Plus, ipsec provides correct manpages and documentation, which wireguard still does not to this day - they only refer to linux-specific tools and configuration on every platform. If they couldn't even be bothered providing documentation with decent quality, I wouldn't want to find out about the quality of their code...

 

[ralphbsz]

What is your network bandwidth? Both how much you have installed in hardware (the bottleneck), and how much you really expect to need/use (the demand)?

I would think that for most common household network speeds, something like an Arm or Intel Atom would do ipsec or a VPN just fine on a single core, at much lower GHz.

 

[ArgentoSoma]

Hi all!

I have the option of choosing a virtual server with 1 or 2x5.5 GHz cores.

This server will act as a high-performance VPN server for VPN connections between 2 or 3 computers. ZFS dataset backups will be sent over the network.

Questions:

1. How much will adding a second core help me with Wireguard performance?

2. Will a second core significantly improve my system, and will Wireguard utilize the second core properly?

3. How can I see Wireguard's core usage?

Thank you!

1 core ARM64 on Netcup and I obtained 300-400 Mbps on Wireguard single-thread (using Docker for CPU/RAM control)