slow speeds according to btest

Hey guys,

Sorry if this has been asked before - I did a search and couldn’t find the answer.

I am currently running hEX S (v6.43.14) with a wAP ac (v6.43.14) + bunch of dumb switches (some of them could be 100Mbps) and wiring has become a total mess. So, I’ve decided to fix that by getting a managed switch and moving all my computers to that switch. In order to avoid downtime, I’ve decided to pick up another hEX S (v6.47.3) and a cAP ac (v6.47.3). This way I will be able to configure everything just the way I want it before replacing “production” configuration.

I’ve just finished configuring everything:

  • 3 VLANs
  • CAPsMAN with 5 wifi networks (2x home, 2 guest, 1 iot)
  • As of now, no firewall rules have been added other than the masquerade one
  • managed switch

So far so good. Then, I wanted to test my speed with btest between cAP (client) and hEX (server).
Tx/Rx: 190 / 190 over TCP with 0 packet loss
Tx/Rx: 975 / 330 over UDP with ~400 packet loss

When I was running same test between my new hEX (client) and old hEX (server), I was getting:
Tx/Rx: 90 / 42 over TCP with 0 packet loss
Tx/Rx: 12 / 58 over UDP with ~600 packet loss

Also, just like in this topic (http://forum.mikrotik.com/t/btest-traffic-generator-testting-bandwidth-of-the-link/130621/1), CPU utilization is 100% on btest server and around 50%+ on the client.

Are those expected results? if so, how come? I thought both hEX S and cAP ac have 1Gbps NICs.

Thanks for your help!

btest itself is very heavy on CPU, this is a well known issue, which has nothing to do with the actual routing performance of your devices. Search the forum again, this has been discussed tons of times.