Download to read offline
![Game
BWRa IPv4 BWRa IPv6
Engine
E[P]
pps
Unreal T 2003
Unreal 2.0
29.5
25
62%
46%
Quake III
Id Tech 3
36.15
93
65%
50%
Quake II
Id Tech 2
37
26.38
66%
51%
Counter Strike
GoldSrc
41.09
24.65
68%
53%
Halo 2
Halo2
43.2
25
69%
54%](https://image.slidesharecdn.com/ciberspects2011presentation-131118103102-phpapp02/75/Influence-of-the-Router-Buffer-on-Online-Games-Traffic-Multiplexing-33-2048.jpg)
Uploaded byJose Saldana
Influence of the Router Buffer on Online Games Traffic Multiplexing
The document discusses the efficiency of communication technologies in gaming, focusing on bandwidth saving and packet handling techniques. It presents metrics on one-way delay, packet loss, and the performance of multiplexing strategies in various gaming scenarios. The results indicate significant improvements in bandwidth utilization and latency reduction, offering insights into optimizing network resources for online games.
More Related Content
Similar to Influence of the Router Buffer on Online Games Traffic Multiplexing
Influence of the Router Buffer on Online Games Traffic Multiplexing
- 2.
- 3.
- 19. 40 50 6070 80 90 100 110 bytes
- 20.
- 22.
- 25.
- 26. Players . . . Player and localagent Access router Internet Game Server
- 27.
- 28.
- 29. Players Wireless link Multiplexer TCM Wireless link . . . TCM Internet Multiplexer Wirelesslink Players Multiplexer Players TCM Game Server
- 30. Native traffic ... Multiplexed traffic . .. PE PE PE PE ... ...
- 31. Payload Payload Reduced Header ... UDP Reduced Header IP PPPMux PPP L2TP IP
- 32. L2TP PPP header hea. IPheader CH PPP Mux Reduc. header Payload MH RH P ... PPP Mux Reduc. header Payload MH RH P Four IPv4/UDP client-to-server packets of Counter Strike η=61/89=68% One IPv4/TCM packet multiplexing four client-to-server Counter Strike packets η=244/293=83% saving
- 33. Game BWRa IPv4 BWRaIPv6 Engine E[P] pps Unreal T 2003 Unreal 2.0 29.5 25 62% 46% Quake III Id Tech 3 36.15 93 65% 50% Quake II Id Tech 2 37 26.38 66% 51% Counter Strike GoldSrc 41.09 24.65 68% 53% Halo 2 Halo2 43.2 25 69% 54%
- 34. Original trace Client toserver Server to client Player 1 to N Client to server traffic Player 1 Player 2 IP/UDP headers compressed Multiplexed, compressed and tunneled Player 1 Player 1 to N Player 2 period ... Player N Not used ... Player N
- 35. 30%-35% 25%-30% 20%-25% 15%-20% 10%-15% 5%-10% 0%-5% Bandwidth Saving 35% 30% 25% 20% 15% 10% 5% 50 ms 40ms 30 ms 20 ms period 10 ms 0% 20 19 18 17 16 15 14 13 12 11 10 9 8 number of players 7 6 5 4 3 2
- 36. Bandwidth Saving 35% 30% 25% BS 20% 15% 20 players 10% 15players 10 players 5% 5 players 0% 5 10 15 20 25 30 period (ms) 35 40 45 50
- 37. Bandwidth Saving 35% Asymptote 30% 25% BS 20% 15% 20 players 10% 15players 10 players 5% 5 players 0% 5 10 15 20 25 30 period (ms) 35 40 45 50
- 38. Bandwidth Saving 35% 30% BS 25% 20% 15% T 10ms T20ms 10% T 30ms T 40 ms 5% T 50ms 0% 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 number of players
- 39. 5 players 10 players 15players 20 players Packet size in bytes 1400 1200 Packet size grows linearly bytes 1000 800 600 400 200 0 native 5 10 15 20 25 30 Period in ms 35 40 45 50
- 40. Average Retention Time 20players 30 15 players 25 10 players 5 players ms 20 15 10 Retention time is half the period avg 5 0 5 15 25 Period in ms 35 45
- 42. Tretention Tprocess Tqueue Tnetwork Tprocess IP network . . . MUX DEMUX GameServer Players IP TCM IP
- 43.
- 44. Offline post-processing Real Trafficin a testbed Buffer Network, processing delays Game traffic Background Router Traffic Generation Traffic Capture Traffic Trace Final Results
- 46. One way delayfor game traffic 200 delay native 180 delay mux 25ms 160 delay mux 50ms OWD (ms) 140 120 100 80 60 40 20 0 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 47. One way delayfor game traffic 200 delay native 180 delay mux 25ms 160 delay mux 50ms OWD (ms) 140 120 100 80 25 + 5 ms 60 12,5 + 5 ms 40 Added mux delays 20 0 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 48. One way delayfor game traffic 200 delay native 180 delay mux 25ms 160 delay mux 50ms Bandwidth saving 120kbps OWD (ms) 140 120 100 80 60 40 20 0 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 49. Packet loss forgame traffic 18% loss native 16% loss mux 25ms 14% loss mux 50ms packet loss 12% 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 50. Packet loss forgame traffic 18% loss native 16% loss mux 25ms 14% loss mux 50ms packet loss 12% 10% 8% Bandwidth saving 6% 4% 2% 0% 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 51. Packet loss forgame traffic 18% loss native 16% loss mux 25ms 14% loss mux 50ms Small saving increase, but double packet size packet loss 12% 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 52. One way delayfor game traffic 200 delay native 180 delay mux 25ms 160 delay mux 50ms OWD (ms) 140 120 100 80 60 40 20 0 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 53. One way delayfor game traffic 200 delay native 180 delay mux 25ms 160 delay mux 50ms Buffer delay reduction OWD (ms) 140 120 100 80 60 40 Added mux delays 20 0 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 54. One way delayfor game traffic 200 delay native Bandwidth saving 120kbps 180 delay mux 25ms 160 delay mux 50ms OWD (ms) 140 120 100 80 60 40 20 0 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 55. Packet loss forgame traffic 18% loss native 16% loss mux 25ms 14% loss mux 50ms packet loss 12% 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 56. Packet loss forgame traffic 18% loss native 16% loss mux 25ms 14% loss mux 50ms packet loss 12% 10% 8% Bandwidth saving 6% 4% 2% 0% 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 57. Packet loss forgame traffic 18% loss native 16% loss mux 25ms 14% loss mux 50ms packet loss 12% Big BG packets discarded Native ones are small 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 58. Packet loss forgame traffic 18% loss native 16% loss mux 25ms 14% loss mux 50ms Small saving increase but double packet size packet loss 12% 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 850 Background traffic (kbps at link level) 900 950 1000
- 59. Packet loss BackgroundTraffic 20% native time limited 18% mux 25ms time limited mux 50ms time limited 16% native high capacity packet loss 14% mux 25ms high capacity mux 50ms high capacity 12% 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 Background traffic (kbps at link level) 850 900 950 1000
- 60. Packet loss BackgroundTraffic 20% native time limited 18% Buffer size does not significantly modify BG packet loss mux 25ms time limited mux 50ms time limited 16% native high capacity packet loss 14% mux 25ms high capacity mux 50ms high capacity 12% 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 Background traffic (kbps at link level) 850 900 950 1000
- 61. Packet loss BackgroundTraffic 20% native time limited 18% Bandwidth saving is always beneficial for BG traffic mux 25ms time limited mux 50ms time limited 16% native high capacity packet loss 14% mux 25ms high capacity mux 50ms high capacity 12% 10% 8% 6% 4% 2% 0% 500 550 600 650 700 750 800 Background traffic (kbps at link level) 850 900 950 1000
- 64.