WireGuard / wireguard-vyatta-ubnt

WireGuard for Ubiquiti Devices
https://www.wireguard.com/
GNU General Public License v3.0
1.46k stars 69 forks source link

Consider adding performance or ballpark figures to readme #30

Open hak8or opened 4 years ago

hak8or commented 4 years ago

It is awesome that this project exists, it is a factor for me looking into what router to buy (microtik vs Ubiquity). Sadly, I cannot seem to find any benchmarks anywhere online for how well this runs on an ER-X, ER-4, ER-Lite, or a older Edge router. For example, on an ER-4 are we talking 10 Mbps with 512 Byte packets, 100 Mbps via fast.com without mentioning packet size, etc? Even an idea of hundreds vs tens of Mbps is still very helpful.

FossoresLP commented 4 years ago

Hi @hak8or, thank you for the suggestion. Even getting ballpark figures would need quite a bit of involvement from the community to cover the large range of EdgeOS devices. If anyone would like to contribute data please comment here and I will enable the Wiki so we can collect those figures there.

dc361 commented 4 years ago

Did we want to create a reporting template? How about something like: Local End Wireguard Version Wireguard Tools Version EdgeOS version (V1.10.x, V2.0.x..) Device (ER4, ERX, ERX-SFP, USG..) Local inbound speed in mb/s Local outbound speed in mb/s

Remote End Wireguard Version Wireguard Tools Version OS Device Remote inbound speed in mb/s Remote outbound speed in mb/s

Results (Local to Remote) Test throughput in mb/s for local send Test throughput in mb/s for local receive Test local cpu load (percent) Test remote cpu load (percent)

Results (Remote to Local) Test throughput in mb/s for remote send Test throughput in mb/s for remote receive Test remote cpu load (percent) Test local cpu load (percent)

File sizes, composition and number of iterations could also be specified

FossoresLP commented 4 years ago

@dc361 An issue template is a good suggestion but I think this is way too long for most people to fill out. I will open a new issue regarding creating a template.

Edit: Sorry, I misread reporting template as issue template. As a reporting template this would be nice, although maybe even still a little too complex. Still going to open an issue regarding an issue template though.

dc361 commented 4 years ago

@FossoresLP Fair .. even if we could get the following subset it would be a start:

Peer 1 Platform and version Peer 2 Platform and version Link speed (local) Throughput 1->2, 2->1