Things have changed greatly since this was first posted. On thing to note is that the bulk of the packets sent and received by your viewer are UDP/IP (no end to end tracking of packets at the OS level) not TCP/IP (end to end packet tracking and retransmission as needed). UDP packets if dropped are usually lost. Other changes Textures and Inventory are now sent via HTTP (which is a TCP/IP protocol) however this causes some issues with some network hardware (routers and cable modems) because of the very high TCP connection churn (connections created and deleted very rapidly). There are several issues about this on both the LL and TPV JIRA. Too high a bandwidth setting can cause very strange and difficult to diagnose problems. The recommended speeds are 500 for Wireless (especially if you have multiple devices talking to your Access point), 1000 for DSL connections and 1500 for hardwired to a cable modem.
Facebook
Instagram
Twitter
YouTube
Flickr
[QUICKTIP] Get less lag in seconds by increasing your Maximum Bandwidth!
in Tips and Tricks
A group blog by Secondlife in General
Posted
Things have changed greatly since this was first posted. On thing to note is that the bulk of the packets sent and received by your viewer are UDP/IP (no end to end tracking of packets at the OS level) not TCP/IP (end to end packet tracking and retransmission as needed). UDP packets if dropped are usually lost. Other changes Textures and Inventory are now sent via HTTP (which is a TCP/IP protocol) however this causes some issues with some network hardware (routers and cable modems) because of the very high TCP connection churn (connections created and deleted very rapidly). There are several issues about this on both the LL and TPV JIRA. Too high a bandwidth setting can cause very strange and difficult to diagnose problems. The recommended speeds are 500 for Wireless (especially if you have multiple devices talking to your Access point), 1000 for DSL connections and 1500 for hardwired to a cable modem.