Bug 2727 - maxExpectedThroughput in vht-wifi-network is too low
maxExpectedThroughput in vht-wifi-network is too low
Status: RESOLVED INVALID
Product: ns-3
Classification: Unclassified
Component: wifi
unspecified
All All
: P3 normal
Assigned To: sebastien.deronne
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-15 20:54 UTC by Alexander Krotov
Modified: 2017-04-18 14:08 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Krotov 2017-04-15 20:54:23 UTC
examples/wireless/examples-to-run.py lists

vht-wifi-network --simulationTime=0.1 --minExpectedThroughput=5 --maxExpectedThroughput=555

However, highest data rate is 866.7 for VHT MCS 9 with short guard interval.

It is easy to get throughput higher than 555:

$ build/examples/wireless/ns3-dev-vht-wifi-network-debug  --simulationTime=1.0 --minExpectedThroughput=5 --maxExpectedThroughput=555 --mcs=9
MCS value               Channel width           short GI                Throughput
9                       40 MHz                  0                       158.505 Mbit/s
9                       40 MHz                  1                       174.956 Mbit/s
9                       80 MHz                  0                       319.506 Mbit/s
9                       80 MHz                  1                       349.677 Mbit/s
9                       160 MHz                 0                       564.4 Mbit/s
9                       160 MHz                 1                       611.657 Mbit/s

I am changing some code in Wi-Fi initialization now and assigned streams are a bit different, so I get different throughput and test fails.

How about increasing maxExpectedThroughput to 866.7? Maybe some overhead should be taken into account, but maxExpectedThroughput should be some theoretically computed upper bound, not just some value slightly above the one developer got when he ran an example.
Comment 1 sebastien.deronne 2017-04-18 14:08:02 UTC
This depends on simulation time. For a very low simulation time, we cannot reach such a high value. That is why in the latest ns-3-dev, this is now an attribute (mainly used for regression, where we need to limit the simulation time!).