` Returning to the subject of this thread, "AQL and the ath10k is
lovely", I'm 100% convinced that it's a fact. It is lovely,
including with Batman.
For reasons I do not understand, I am unable to make satisfactory
tests with Flent/netperf. Instead of test results, here's an
anecdote based on visual observation.
On a pre-AQL build and on a post-AQL build of OpenWRT, I ran the
same home-brew test, which was to view in real time a ping job to
google.com and, after watching it a while, to begin simultaneously
downloading a large file into the same host that was doing the
pinging. Although the two setups were not identical, the
performance contrast was satisfactorily demonstrated, I believe.
On the pre-AQL setup, the pings were *fairly* consistently around
20ms until the download started. Then they became much slower and
much less consistent, typically running around 80ms and as high as
1300ms. The download job was an rsync with the --progress flag so
I could see the consistency of the download speed. The download
speed was very inconsistent, varying between 100 and 700
kilobytes/sec. (I have been dismayed by this kind of performance
for a long time now.)
On the post-AQL batman setup, the pings were consistently around
17ms, regardless of whether the download job was running. The
progress of the download job was also consistent, staying around
550 kilobytes/sec.
It was a visually stunning contrast that made me involuntarily
shout "Wow". My wife came in to watch, and was similarly
impressed.
`
