That is around the figure you can expect from a 720 MHz mips 74Kc single core CPU (QCA9558) - and in practice your traffic is very jagged and laggy at the top of that throughput.
That's a totally meaningless figure, you're effectively only testing the RAM bandwidth here, which has no direct impact on the routing abilities of your device (data coming on WAN, being processed by netfilter, router, NATed, going out to LAN).
applies to your situation, ath79 is far beyond its abilities for that.
[these two posts don't belong into the 22.03.3 announcement thread, as it's not specific to this release at all - earlier releases (21.02.x, 19.06.x, …) can't get any more out of this hardware either - just that half a decade ago, fewer users had the WAN speeds to even notice these hardware limits]
Netgear R7800 and Buffalo WZR-HP-AG300H routers upgraded from 22.03.2 to 22.03.3 with settings retained and missing packages reinstalled post-upgrade.
Both upgrades were uneventful.
Thank you devs for the great release!
@phinn are you having the isolation issue with the master snapshot build noted by others on mvebu - principally the wired LAN being invisible to WLAN clients? Are you using the latest master snapshot or an older one? Did you retain your configuration file or start fresh?
If I would get along with DSA I would give the Snapshot build a try. I'm still using 19.07 and I think that I have to move to an up-to-date Build (security wise)
Oh dear. That's embarrassing. Thank you for pointing out the obvious for me.
On another note; I did not remember at all that there are two packages - but since one of them, i.e. the non-UBI one is not recommended (or practically usable...) anymore - why is that the one that has the "obvious" link on the main page for the router?
Wouldn't it be better for it to be the UBI one of there has to be only one link?
Devices featuring the MV88E6176 integrated switch are currently broken in 22.03: the switch behaves as a hub, meaning network packets will be sent to all ports. This bug is documented in (FS#11077). This problem is only seen with kernel 5.10. OpenWrt 21.02 and OpenWrt master are not affected.