All performance tests were done with Android app 22.214.171.1243102 and 126.96.36.199788 firmware using select tests from the Version 10 Router process.
The iperf3 WAN to LAN and LAN to WAN throughput tests came in at 833 and 672 Mbps, respectively, highlighted in the charts below. This was a little better than Velop TB for downlink, a little worse for uplink.
Routing throughput - iperf3 method
WAN to LAN testing using the tougher HTTP method benchmarks shows similar results for both Velops, with both being outdone by GWifi
Routing throughput - HTTP Score comparison - WAN to LAN
Plot key file size: [A] 2 KB, [B] 10 KB, [C] 108 KB and [D] 759 KB file
LAN to WAN shows essentially the same pattern. In all, either Velop's routing performance should be fine unless your internet connection is over 500 Mbps.
Routing throughput - HTTP Score comparison - LAN to WAN
Note these results were obtained with the default Express Forwarding setting enabled. This switch is available only if you access the web admin GUI (Connectivity > Administration). I did not run tests with this setting unchecked.
Velop DB was run through our Wi-Fi System test process, letting it use whichever channels and bandwidth it chose. It used 2.4 GHz channels 1, 4 and 7 for Root, Hop 1 and Hop 2 nodes, respectively and 5 GHz Channel 36 for all three nodes. So this tells us Velop is using 5 GHz for backhaul. The octoScope Pal logs showed the Root node using 40 MHz banwidth, but the other two nodes using 20 MHz bandwidth.
Velop DB in test chamber
Throughput vs. Attenuation (RvR)
The Rate vs. Range or RvR benchmarks look at how throughput varies with decreasing signal. This test is done on the root node, so is a best-case view and does not include any effects from backhaul links.
I usually have to add 9 dB of attenuation when running 2.4 GHz tests so that the octoScope Pal reference client's -30 dBm maximum recommended input level is not exceeded. But this wasn't necessary with Velop DB, which indicates lower transmit power than Velop TB, where I had to apply the additional 9 dB.
The 2.4 GHz downlink plot shows Velop DB starting out midway between Google and Velop TB, but starting its decline almost immediately to join GWiFi's curve at around 30 dB. Pal data showed DB was running in 40 MHz bandwidth, which should have given it more of an edge over GWiFi, which is limited to using 20 MHz bandwidth in 2.4 GHz.
Throughput vs. Attenuation - 2.4 GHz downlink
2.4 GHz uplink shows similar results.
Throughput vs. Attenuation - 2.4 GHz uplink
5 GHz downlink shows generally disappointing results for Velop DB. Pal logs indicated a maximum Tx link rate of 650 Mbps and Rx rate of 520 Mbps, which could account for the lower results.
Throughput vs. Attenuation - 5 GHz downlink
The DB's throughput improved for 5 GHz uplink, even with similar maximum link rates reported.