hEX RB750Gr3 with MT7621 chip can use simple bridge without vlans (and without stp and igmp-snooping). In this case hEX can switch untagged traffic beetwin all its ports on wire-speed with no impact on CPU (~900Mbit/sec between hosts in my case - the result could be limited by SSD perfomance).
Other option is using cpu-switching bridge with vlans like described here:
https://wiki.mikrotik.com/wiki/Manual:B ... witch_chip
Principle device schema shows 1G-link from switch chip to cpu:
https://i.mt.lv/cdn/product_files/RB750 ... 190642.png .
In my tests cpu-switching bridge setup demonstrates speeds beetwin two hosts about 900Mbit/s (like in switchchip bridge setup) with overoll cpu load up to 30% and single core load up to 50-60% (proccess "networking").
So I can conclude, that CPU power is enoth for cpu-switching at full-duplex 1G-speed devided for all 5 device ports. Such traffic profile can be seen in a number of SOHO networks, so hEX with vlans in cpu-switching bridge could be sutible for them.
My configuration for cpu-switching bridge was:
/interface bridge add name=bridge1 igmp-snooping=yes protocol-mode=none
/interface bridge port add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether1
/interface bridge port add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=ether2 pvid=5
/interface bridge port add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=ether3 pvid=5
/interface bridge port add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=ether4 pvid=5
/interface bridge vlan add bridge=bridge1 tagged=ether1 untagged=ether2,ether3,ether4 vlan-ids=5
/interface bridge vlan add bridge=bridge1 tagged=ether1,bridge1 vlan-ids=100
/interface vlan add interface=bridge1 name=MGMT vlan-id=100
/ip address add address=172.24.0.102/24 interface=MGMT
/ip route add distance=1 gateway=172.24.0.1
/interface bridge set bridge1 vlan-filtering=yes