Question about the output file content of example.py

[kakachch]

The Bandwidth in the output file starlink-5-5-550-53-grid-LeastDelay/perf-13-14_4.txt after running the example.py code is different from the "satellite link bandwidth (\"X\" Gbps)": 5 specified in config.json.

the content of perf-13-14_4.txt :

Connecting to host 10.0.18.20
, port 5201
[  4] local 10.0.25.40 port 41256 connected to 10.0.18.20 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  1.55 GBytes  13.3 Gbits/sec   21   14.1 KBytes       
[  4]   1.00-2.00   sec  1.72 GBytes  14.7 Gbits/sec    0   14.1 KBytes       
[  4]   2.00-3.00   sec  1.80 GBytes  15.5 Gbits/sec    0   14.1 KBytes       
[  4]   3.00-4.00   sec  1.82 GBytes  15.7 Gbits/sec    0   14.1 KBytes       
[  4]   4.00-5.00   sec  1.82 GBytes  15.7 Gbits/sec    6   14.1 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-5.00   sec  8.70 GBytes  15.0 Gbits/sec   27             sender
[  4]   0.00-5.00   sec  8.70 GBytes  15.0 Gbits/sec                  receiver

iperf Done.

[xiex386]

Thanks for your feedback.
It's because the tc misunderstands "Gbps" as "GBps". #19 has fixed that.

[kakachch]

Thank you for your response.
I have pulled the latest code and re-run the example, but the bandwidth in starlink-5-5-550-53-grid-LeastDelay/perf-13-14_4.txt is still different from config.json.
And if I change "satellite link bandwidth (\"X\" Gbps)" in the config.json to 10, the iperf bandwidth in the output file not change.
If possible, could you show the example's results from your side?

[xiex386]

Could you please show your tc configuration of container?
Commands like this: $ docker exec -it ovs_container_1 tc qdisc
Output like this:

qdisc noqueue 0: dev lo root refcnt 2
qdisc noqueue 0: dev eth0 root refcnt 2
qdisc netem 8012: dev B1-eth2 root refcnt 5 limit 1000 delay 46.3ms rate 5Gbit
qdisc netem 8013: dev B1-eth5 root refcnt 5 limit 1000 delay 46.2ms rate 5Gbit
qdisc netem 8043: dev B1-eth6 root refcnt 5 limit 1000 delay 32.3ms rate 5Gbit
qdisc netem 805a: dev B1-eth21 root refcnt 5 limit 1000 delay 50.3ms rate 5Gbit

[kakachch]

After I input the docker exec -it ovs_container_13 tc qdisc，
Output:

qdisc noqueue 0: dev lo root refcnt 2
qdisc noqueue 0: dev eth0 root refcnt 2
qdisc netem 82a4: dev B13-eth12 root refcnt 2 limit 1000 delay 46.3ms rate 5Gbit
qdisc netem 82a3: dev B13-eth14 root refcnt 2 limit 1000 delay 46.2ms rate 5Gbit
qdisc netem 82c5: dev B13-eth8 root refcnt 2 limit 1000 delay 36.6ms rate 5Gbit
qdisc netem 82d1: dev B13-eth18 root refcnt 2 limit 1000 delay 47.0ms rate 5Gbit
qdisc netem 82e0: dev B13-eth27 root refcnt 2 limit 1000 delay 7.1ms rate 5Gbit

But the StarryNet/starlink-5-5-550-53-grid-LeastDelay/perf-13-14_4.txt is:

Connecting to host 10.0.18.20
, port 5201
[  4] local 10.0.25.40 port 42736 connected to 10.0.18.20 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  1.37 GBytes  11.8 Gbits/sec    3   14.1 KBytes       
[  4]   1.00-2.00   sec  1.76 GBytes  15.1 Gbits/sec    0   14.1 KBytes       
[  4]   2.00-3.00   sec  1.84 GBytes  15.8 Gbits/sec    0   14.1 KBytes       
[  4]   3.00-4.00   sec  1.84 GBytes  15.8 Gbits/sec    0   14.1 KBytes       
[  4]   4.00-5.00   sec  1.84 GBytes  15.8 Gbits/sec    0   14.1 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-5.00   sec  8.65 GBytes  14.9 Gbits/sec    3             sender
[  4]   0.00-5.00   sec  8.65 GBytes  14.9 Gbits/sec                  receiver

iperf Done.

[xiex386]

Strange... The result in my machine is OK.
It looks like the tc is set but not works.
What's your environment? CPU architecture, Linux kernel version, distribution, and any virtualization

[kakachch]

My environment:
CPU architecture: x86_64
Linux kernel version: 5.4.243
Distribution:

Distributor ID: Ubuntu
Description:    Ubuntu 20.04.6 LTS
Release:        20.04
Codename:       focal

The virtualization: none

I feel strange as well.
If it still doesn't work, I'll deploy it on my personal PC to confirm whether it's an issue with the current machine.