Bug #13405
open
Wireguard: The webgui becomes excessively slow to respond with a large number of peers
Added by Steve Wheeler over 1 year ago.
Updated 6 months ago.
Affected Plus Version:
22.05
Affected Architecture:
All
Description
Webgui pages that include data from Wireguard can become very slow to respond with a large number of elements present (peers/tunnels).
Code that parses the output of 'wg show all dump' creates a delay.
For example we see delays of ~10s opening the Wireguard status page with 80 peers defined on a 6100.
This affects the peers, tunnels and status pages. And to a lesser extent the dashboard when the Wireguard widget is disaplayed.
I can confirm high delay in webgui response when loading wireguard UI.
I can also confirm very high CPU usage when using the Wireguard widget. Can this be addressed as it is also still an issue on 2.7 beta so has not been addressed.
- Plus Target Version changed from 22.11 to 23.01
I can also confirm that 50 WG peers are killing a 1537 Max device. Making changes is painful, doubled when I have to make changes to 2 devices in an HA pair.
- Target version deleted (
2.7.0)
- Plus Target Version deleted (
23.01)
I can also confirm this, but its happening to me with only some Peers (exactly, 4 tunnels, about 10 peers in total) I've checked the output of "wg show all dump" but in terminal is kind of instant, no any delay.
Adding any widget to main dashboard related to Wireguard makes dashboard also slow.
+1 - Adding Wireguard widget to dashboard makes the dashboard load extremely slowly. Also the menus relating to wireguard are slow to load.
Later edit: 2.7.0-RELEASE at this time.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by