Quote:
|
I don't know why you keep banging on about proxies where it's totally irrelevant. The speed of network devices is not infinite. A transparent proxy is not required for a network device to slow down.
|
Because as I point on in the thread, a bad transparent proxy
could explain why HTTP traffic alone is throttled and not other traffic.
I concede there are lots of other reasons that could also explain slow HTTP connection/speed tests but if a network device slows down because it's overloaded, it tends to slow down all traffic.
That isn't "banging on" about something. It was asking a question, admitting by saying "am I making sense". How very rude.
All I was trying to point out was that for one type of traffic to be slowed down compared to others suggests that there is either something (and I admitted I didn't know what) was managing that traffic or the target server/connection (or route to that server) was overloaded. That could be a proxy server or HTTP traffic shaping/QOS (and most firewalls can throttle traffic).
I couldn't quite believe that speedtest.net itself could be at fault but it looks like this is the case. The Preston node (automatic choice for me) is struggling to get over 10MBit/s this morning but London and vmspeed.com report 50Mbit/s.
Whether the finger is still pointed at VM is looking less likely although it's still possible that the routing that's slow is still within VM's core network. I haven't got the energy to start looking at traceroutes.
Cheers, Rob.
---------- Post added at 10:26 ---------- Previous post was at 10:22 ----------
Another thread on why Preston speedtest.net is not the most reliable of nodes for testing:
http://community.virginmedia.com/t5/...ts-wrong-with-
speedtest-net/td-p/1132073
Cheers, Rob.