2 months??? wAP ACs took nearly a year to get stable numbers.
In that specific case, a special situation is presented, which was the incorporation of a new ipq4xxx platform and a massive support for the ARM architecture
Are you sure you are talking about wAP ac
and not cAP ac
? The wAP ac
is MIPSBE, not ARM.
Yeah the wAP AC was a terrible WAP when it first released. The processor in it wont allow it to get anywhere near the 866 that it should. And when it first came out... 35 M was the standard. After months and months of updates they got it around 180M.
The cAP ac had similar results out of the gate and can now get into the low 300s. But... I am seeing way too many disconnect messages and finding that it just can't handle crowded environments. Mikrotik was able to reproduce the problem and emailed after I posted enough times that "THEY DON'T GET BACK TO ME", that they currently have no fix.
I found a fix. I paid the $200 difference out of pocket to get a Ruckus R510 in the same spot. It had no problems keeping clients connected.
Disclosure... I have tried to work with Mikrotik on wireless problems a few times before. Support would send me one email PER MONTH, will things to "TRY". I finally gave up on that install as it would have a radio just refuse to accept clients. Pulled it and swapped to Ruckus... complaints stopped.
Last month... client was complaining about his remotes not staying connected to the wifi... and every weekend it would not connect at all. Found it was at its worse when they had a weekly street vendor event. Saw a lot more wireless interference... swap out Tik WAP... Problem solved.
On the most recent replacement... client was calling constantly about low throughput and connection issues. Swapped manufactures... problem solved again.
I love Mikrotiks as routers... but as WAPs... just too many "gotchas". After trying and hoping customers would be ok with the caveats... THEY WERE NOT!
I wasted a ton of time writing cool scripts and schedules tests for caps-man managed systems.
Cutting off the Guest SSID when the primary gateway goes down.
Timers for when SSIDs would broadcast.
Schedules to adjust for time on specific days. (Schedules only happen at a time... I wasted time writing scripts that would check day vs time every 5 minutes. So if you turned the router on it would not miss a schedule as it would constantly check schedule vs state.)
Per client bandwidth limiting
Private PSK for company managers to allow for removal off one person and not having to use anything like Active Directory or change the password on every device around the building.
Trust me... I am not happy that I have to remove Mikrotik wireless from all my bids. And I keep having to replace the installs I put in at cost to "make the customer happy".
"It ain't what you don't know that gets you into trouble. It's what you know for sure that just ain't so."