i could make use of wireshark and TCP/UDP connection list and reverse DNS and traceroute the true identity and location of all relevant connections to any specific server that retrieves content for assets such as textures, objects, sounds, etc.
i could then narrow down the issue to a specific server in a specific location by measuring the downstream speed of that particular server.
i am currently using the Firestorm client set to "Phoenix", the latest version.
the bandwidth settings within the client is really just a simplified setting for the amount of multiple simultaneous connections the client can make to any given server for asset retrieval.
there are network speed throttle settings within the debug menu that also affect upload and download connection speeds as well but despite changing any of these settings inside the menu and debug menu, the network speed observed inside the statistics window of the client still shows a maximum speed of 1Mbit/s (changing texture retrieval from UDP to TCP makes no difference)
its my opinion and thought, despite any additional detailed testing that i may perform, the results i will receive will be indicative of a server that is speed limited to 1Mbit/s, a latency issue in the traceroute path or a peering issue.
i have measured the same instances with the latest official stable release of the SL client as well.
now i dont doubt that this could be a peering/latecny issue between my ISP and CDN servers and/or LL's servers, the statistics settings does not measure the latency of independent connections, only as a whole measurement for latency and packet loss.
average packet loss measured in the statistics window is less than 1%, latency averages 300mS, after complete loading of 128m far clip area of a region, typically less than 5 minutes.
it would be nice to see what others network speed is observed through the statistics menu.
ill get around to performing more detailed tests to try and pin down the actual issue though im very confident the issue is not my network and client, the issue is either a peering issue between the CDN/LL and my ISP or that one or more servers are simply throttling their outbound speed to a single IP despite multiple connections (its common in the IT industry to do this)
i also dont see any method to change the VFS size for the cache either (similar to virtual memory), it appears to be hard-coded to 1GB.
since i have visited many regions over the weekend, their assets have been saved to the cache, re-entering those regions provides instant load-up of those assets with extremely minimal load time, current cache size is 4.1GB, only changed > objects, sounds, textures and avatars are refreshed, non changed assets are retrieved from the cache.
at the current time, i have the viewer configured to draw "grey" outlines of unloaded assets, its a far cry from the "missing image" days.