So I did a quick test on a heavily loaded 5.8 sector running 3.10 and about 40 CPEs connected (NStream+Polling), average latency was about 80ms to the client, but after changing the Max Station Count to 60 (I took a wild guess and picked the number of CPE's connected * 1.5), the average latency dropped down to 40ms! Changing the Max Station Count back to the default of 2007 increased average latency back up to 80ms, and then back to 60 and again back to 40ms ping averages.
Another test on an AP with the new test package shows less dramatic, but still improved resultes on latency, averages were roughly the same (from 6ms to 5ms), but jitter was noticably less and max ping times were about half (from 61ms to 32ms).
Had a customer call in yesterday with a SR9 CPE yesterday that couldn't maintain a radio link to the tower for more then 2-3 seconds, this AP was running the new NStream Test package. Changed the max station count from the default 2007 down to 1.5 times the number of CPEs connected, and his CPE has not disconnected yet in 18 hours.
It seems the support documentation for this setting needs to be revised along with alot of testing to find out just what this setting really effects, and some input from the programmers to find out what a good value for this should be (I'm sure my 1.5 times the number of connected CPEs can be improved on)
Has anyone else noticed this about the Max Station Count? In the past we have always just left it default thinking it was a pretty much useless option.max-station-count (integer: 1..2007; default: 2007) - maximal number of clients allowed to connect to AP. Real life experiments (from our customers) show that 100 clients can work with one AP, using traffic shaping
What everyone else have yours set to? Do you see similar improvments to mine when changing it?