From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Performance v/s signal quality graph.
Date: Fri, 25 Jul 2014 16:15:26 -0700 [thread overview]
Message-ID: <53D2E50E.5010205@candelatech.com> (raw)
Some time back, I ran some tests, and someone (sorry, can't remember or find the email)
suggested my signal might be too hot. I was using a 30 db fixed attenuator inline with the SMA
cables.
I set up a test today with E5 processor system as station, and a fast i7 processor
system as AP, with the two systems cabled through our variable attenuator. Open authentication,
channel 149, other wifi equipment in area on 5ghz was (mostly) idle or powered down.
Kernel is 3.14.13+, latest ath10k CT (10.1.467 based) firmware on both systems
(though I don't think that matters much for throughput tests). 10 virtual stations
configured on station machine, but only one was actively doing traffic.
Here is a udp download v/s rx-signal graph as the attenuator is stepped from 0 to 95.5
db attenuation in .5 db steps.
http://www.candelatech.com/pdfs/ath10k_atten_vs_throughput.pdf
The rx-signal axis is the left hand side. The green graph is the station's (ie netdev)
rx bps, the black is UDP goodput.
It seems ath10k (WLE900VX) has no real trouble with hot signals, and runs best between
-15 and -52 rx signal level (as reported by the station device).
Our systems are not perfectly isolated, so the maximum attenuation is around -85.
Enjoy,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2014-07-25 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 23:15 Ben Greear [this message]
2014-08-05 15:15 ` Performance v/s signal quality graph Bart Jooris
2014-08-05 15:25 ` Bartosz Markowski
2014-08-05 16:35 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53D2E50E.5010205@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.