hAP be lite performance issues

hap ax S is even better comparison, as they cost exactly the same, and hap ax S is a good device. at least in our testing there were no apparent problems with it.

I have the ax s and the ax2. The ax2 is faster in any aspects, Wi-Fi performance is up to 50% better than ax s.

To be fair, the ax2 costs 88 EUR and the ax s around 68...

And, the ax s has an USB port and an SFP cage as well, which I don't need.

Well, a crippled SFP cage at least . . . Not sure why anyone would bother with anything short of SFP+ in this day and age . . .

Same here: hAP be lite as a pure AP on RouterOS 7.25.1 (no firewall/NAT/queues, bridge with VLAN filtering, MLO disabled). Wi-Fi throughput on a 500 Mbit/s line pushes the CPU to ~90–95 %.

Ethernet receives everything via fast path, while the wifi interfaces show zero fast path packets in both directions. Downstream traffic therefore runs half fast path, and upstream runs entirely in slow path.

The result is the same regardless of uplink port (ether2 or ether3) and whether 5 GHz runs 5ghz-ax or Wi-Fi 7.

CPU profile: /tool profile duration=10s during the download phase:

mt76             24.0%
mac80211         21.7%
bridging         12.0%
kernel           11.0%
mt7996e           8.7%
networking        5.2%
ecnt_eth          4.0%
total            89.2%

/tool/profile cpu=all freeze-frame-interval=1 duration=3

Taken from docs. shows usage per core.

/tool profile cpu=all duration=5 (at peak download):
cpu0   85.5%  (mac80211 21%, mt76 21%, kernel 15%, bridging 11.5%)
cpu1  111.5%  (bridging 20%, ecnt_eth 20%, mac80211 20%, kernel 15.5%, mt76 15%, mt7996e 11.5%)

Both cores are saturated at peak, so this is not a single-core bottleneck. cpu1 also carries the ethernet driver (ecnt_eth 20%) and most of the bridging.

After 1.5 month of ownership and use, extensive testing, multiple configurations, and trying different RouterOS versions (both stable and testing), the performance of this device is simply unacceptable for what it's advertised to deliver.

After years of using MikroTik products, this is genuinely disappointing. I'm going for an RMA!

Just tested with my hAP be lite, and without MLO (I don't know why but devices are unable to get an IP address when MLO is running.) I'm getting 719.9 Mbps DL and 697.5 Mbps UL. I'm using OpenSpeedTest to check speeds. CPU is at around 65-70% while running my test. Running latest beta version.

That's the key. It seems like you have to run latest development build to have the best experience with BE devices.

Thats true as i have an open ticket about the be3 and a fix should be included in 7.26beta6 :slight_smile:

Still, MLD interface isn't working properly for some reason...

There isn't just some issue with MLO; the MediaTek wireless driver isn't optimized, and the same goes for the hAP ax S.
It's not normal to have the CPU at 100% with a transfer speed of around 500/600 Mbps when it's used as a simple AP or cAP.

Yea, I tested MLO yesterday with default config on be lite and no luck... Clients stuck on Obtaining IP address and then disconnects...

Without MLO everything works. But yea, drivers need improving...