I use it for the polling features.. havenāt played with it enough to find the best settings for maximum throughput. I notice the biggest improvements with lots of clients connected to an AP with Nstreme+polling enabled. With no framer-policy (framer-policy=none).
I have one link with NSTREME Dual enabled for FDX using exact-size, and a frame size of 3500 bytes. I was able to achieve over 20mbps FDX using RB532Aās (UDP). My target was 10mbps, so I didnāt tweak much more than needed.
Iāll have to setup some links on the test bench and get back to you. Iād like to know myself..
t3rm -
From practical experienceā¦you can get over 20Mbps using Nstreme. The caveat is that if you donāt have a lot of traffic then you get latency. I have found that a 10 - 20% load is required to minimize the latency.
wildbill442 is correct in the framer policy = none, that has been my experience. I have seen some mention of setting a policy and making it smaller (closer to 1500 bits) to help cut the lag time down - the trade off is reduced throughput. One of Nstremeās features is the ājumboā size frame it sends across wireless. Bigger āframeā - more data moved - ack same size as smaller frame - so less time spent on acknowledging frame transmissions⦠Nstreme also sends packets in order receivedā¦a plus for VoIP - if you have enough traffic!
The better the signal to noise ratio the better the throughput using Nstreme. 30db between signal and noise seems to be the optimal value⦠20db will net you pretty good results, less than 20 and you are going to have trouble⦠Nstreme is a little CPU intensive so I wouldnāt use it on anything less that an RB532⦠I have seen a few clients setup w/RB133 - not sure how well that is going to work out yet⦠Definitely NOT an RB133 as the āAPā in an Nstreme setup.
Framer policy affects how much the cpu gets involved in ordering the packets in to a jumbo frame. I found that policy=none saves cpu time, it also sends the packets out in the same order received. Best fit would probably my second choice if I had to make one.
Which optoin is best depends on the cpu - what are you using for the wireless platform? The faster the cpu the better able it is able to handle juggling packets in to the Framer Policy you want to use. Like I said above and in my earlier posts, policy=none is my go to. Uses less cpu and memory resources and sends the packets out in the same order receivedā¦
i thought it would be better to stay on the same chain instead of starting a new thread. also it help in bench marking the old firmware settings with the updated firmware settings.