Date: Wed, 17 Apr 2019 17:22:31 +0200 From: "D. Ebdrup" <debdrup@gmail.com> To: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: openvpn and system overhead Message-ID: <CANtgGBr83UW_7LDA9==T3XwMYUCUvnpDuf0jrh7n0Pd_0Hoixg@mail.gmail.com> In-Reply-To: <alpine.BSF.2.20.1904171707030.87502@puchar.net> References: <alpine.BSF.2.20.1904171707030.87502@puchar.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Wojciech, I believe you might've run into one of the design decisions that was made by OpenVPN, specifically related to how it exclusively favours spawning more processes rather than implement any form of threading. I believe it's currently on the roadmap [1] of things that they would like to address at one point, but I'm not aware of any work being done on it at present. [1]: https://community.openvpn.net/openvpn/wiki/RoadMap#Threading Daniel Ebdrup aka. D. Ebdrup. On Wed, Apr 17, 2019 at 5:11 PM Wojciech Puchar <wojtek@puchar.net> wrote: > > i'm running openvpn server on Xeon E5 2620 server. > > when receiving 100Mbit/s traffic over VPN it uses 20% of single core. > At least 75% of it is system time. > > Seems like 500Mbit/s is a max for a single openvpn process. > > can anything be done about that to improve performance? > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANtgGBr83UW_7LDA9==T3XwMYUCUvnpDuf0jrh7n0Pd_0Hoixg>