Throughput limitations when using Simu5G for real-time simulation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 235
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm using the extclientserver example code in the emulation provided by Simu5G for simulation. No matter how I adjust the carrierFrequency and numBands parameters, the simulated throughput doesn't improve. Specifically:
When the carrierFrequency is set to 3.5GHz and numBands is set to {30, 40, 50, 60}, the throughput for both the receiver and transmitter is only 20Mbps when using iperf3 in TCP mode; when using iperf3 in UCP mode, the throughput is only 35Mbps; and when the carrierFrequency is set to 4.9GHz, the throughput remains essentially unchanged.
When the carrierFrequency is set to 3.5GHz and numBands is set to {80, 90, 100}, the throughput for both the receiver and transmitter is only 17Mbps when using iperf3 in TCP mode; when using iperf3 in UCP mode, the throughput is only 30Mbps; and when the carrierFrequency is set to 4.9GHz, the throughput remains essentially unchanged.
Is the throughput of Simu5G limited when performing real-time simulation?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the extclientserver example and its real-time simulation configuration, then reproduce the reported iperf3 TCP and UDP results while varying carrierFrequency and numBands. Compare the observed throughput with non-real-time runs or the example's documented limits; done means identifying and clearly reporting whether real-time simulation imposes a throughput limit and why.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100