Interesting, thanks for the info. Have you tried -smallbuffers too?
Because the 2.4GHz part isn't so stable on newer OpenWrt releases, and people has postulated if it's a side-effect of the changes in ath10k. My experience is that using either the "original" ath10k and the ct version (the first 2 in your list) makes no difference whatsoever, that's, the 2.4GHz part may die after some time.
BTW, my brief test of using -htt is much worse than yours, in fact it's the worst. However, I need to re-test it at another time to try to minimize the neighbourhood interferance.
Using the non-ct firmware and kmod gives the highest result, that's consistent with your result.
Perhaps it's also possible to mix and match ct and non-ct versions too?
If you mean mix and match for example using non-ct kmod and ct firmware, that would create more problems than it solves. I believe I saw a post somewhere from the CT firmware maintainer that doesn't recommend this either.
If the standard qualcomm firmware works for you, why not stick with it?
Same here and we need to get the developers to switch our device to non-ct firmware and kmod because it is just causing issues for people who don't realize this switch must be made to avoid throughput issues.
In other solutions I'm seeing recommendations for the kmod-ath10k-ct-smallbuffers driver. The issue many are having is the new driver uses more memory then the router has and overflows. Has anyone tested this one for connection and throughput?