Anyone else suspect that SS is prioritizing speedtests during peak times so they don't look so bad?
A little background - I've got an issue right now where I can't stream Netflix on my PS3 (using unblock-us) from 5pm or so to 12pm or so. Works perfectly with 1080p Super HD if I stream during the day. Using the bandwidth monitor on my router, I can see that when I stream during the day, it consistently gets around 800-900 KB/s transferring (which is close to line speed for me, fairly long way from the exchange) - and I get the highest quality. When I stream during the peak periods, it transfers at 500KB/s for a few seconds, then drops down to nothing or close to it.
Thing is, even at the peak times when I do a speedtest.net check to San Francisco I get line speed (8-9 Mb/s), but if I do speedtests to less well known servers in the same place, I get around 1Mb/s. Which suggests that slingshot has put the main speedtest.net servers on a priority list somewhere.
It also seems that slingshot's prioritization might be per-connection - my usenet client (which is also connecting to servers in the bay area) always manages to pull line speed, even at peak times - it's just using 20 connections to do it. Shame that netflix doesn't use the same trick!