Please enable JavaScript.
Coggle requires JavaScript to display documents.
Choose packet size, Topology 3 Suburban Area Scenario - Coggle Diagram
Choose packet size
300-500 bytes
Choose No. clients
3 clients
1 client
Choose app size
Heavy
CPU allocation
*5=25%
Delay decreases
1349 ms
Throughput increases
15.43 kb/s
*10=50%
*15=75%
*20=100%
Normal
Bandwidth
0.01
CPU allocation
*5=25%
2 more items...
*10=50%
*15=75%
*20=100%
0.02
CPU allocation
*5=25%
2 more items...
*10=50%
*15=75%
*20=100%
0.03
CPU allocation
*5=25%
2 more items...
*10=50%
*15=75%
*20=100%
0.05
CPU allocation
*5=25%
2 more items...
*10=50%
*15=75%
*20=100%
0.1
CPU allocation
*5=25%
2 more items...
*10=50%
*15=75%
*20=100%
Light
Bandwidth
0.01
0.02
0.03
0.05
0.1
600-800
Topology 3 Suburban Area Scenario
Case 1: Prioritised Clients Get Served At Closer Core (Edge Computing)
Explanation:
When suburbanb clients have to communicate with a faraway core, sufferring from the huge propagation delay, which causes bad QoS.
Prioritised clients can get access to a closer core (lower propagation delay), which is a so-called virtual core, to get a better network performance.
Bandwidth = 100 kb/s
CPU quota = 100%
Throughput increses by: 47.46%
End-to-End Delay decreases by: 32.57%
CPU quota = 75%
Throughput increses by: 68.63%
End-to-End Delay decreases by: 41.45%
CPU quota = 50%
Throughput increses by: 56.53%
End-to-End Delay decreases by: 35.10%
CPU quota = 25%
Throughput increses by: 9.10%
End-to-End Delay decreases by: 5.15%
CPU quota = 5%
Throughput increses by: 6.76%
End-to-End Delay decreases by: 3.92%
Case 2: Prioritised Clients Get Served at Idle Core (Rerouting)
Explanation:
When multi-clients have to sharetext a single core's resource, and its limited computational capacity causes bad QoS.
We offer the option to re-route our prioritised clients to another idle core, which may be further than the current core but have better computation capacity.
Though there will be a trade-off, clients still can get a better network performance out of it.
Bandwidth = 100 kb/s
CPU quota = 100%
Throughput increses by: 20.00%
End-to-End Delay decreases by: 15.32%
CPU quota = 75%
Throughput increses by: 51.85%
End-to-End Delay decreases by: 32.51%
CPU quota = 50%
Throughput increses by: 105.26%
End-to-End Delay decreases by: 50.57%
CPU quota = 25%
Throughput increses by: 306.78%
End-to-End Delay decreases by: 75.83%
CPU quota = 5%
Throughput increses by: 223.53%
End-to-End Delay decreases by: 68.94%