Quote:
|
Originally Posted by Chrysalis
Transferred: 15,000,000 bytes in 3 minutes 2 seconds (80.2 KB/s)
From germany ftp.
Yesterday however I got 1.15mb/sec from creative over http, so clearly its variable depending which peer you go over and if http or not. Remember http downloads might well be of a proxy server so not external traffic.
|
A perfectly legal 15 Mibibytes it is I'm sure
Something you have to understand.... some companies when it comes to peering etc, just get on with it, get it done and plan for the future. Others have departments that faff around with it all, juggling it between their various other responsibilities, and there's no front line access (the alledgedly engineers on both sides have no influence over peering at all, they only get to implement what they are told - nice to see with those salaries comes responsibility I don't think).
Much smaller ISPs than ntl have more people dealing with peering. I could if requested set up a public peering session in a very short while, and have a couple of times harrassed certain other companies over peering interfaces getting towards congestion because congesting external links upsets customers on an even bigger scale than congesting internal or local ones.
So it wouldn't surprise me if some links were still overpopulated, simply because no-one bothered to plan to upgrade them until they were nearly maxed, and because the upgrading was slightly more time consuming than expected or growth of traffic a bit quicker so the pipes are congested.
Just talking from prior experience with certain companies.
In short I don't know what the issues are, however I find the idea of peering being congested fairly easy to swallow as transit is much more looked after than PIs. Really if a PI is congested or public peering it should be shut down immediately to avoid service affect, however doing that instead of transit costs money, which makes you wonder why ntl's *public* peering policy was at least until fairly recently so completely anal / holier than thou.
But yeah pretty much a lot of the belayed upgrade are probably due to bureaucracy, procrastination and over complication, 3 things ntl historically do well to make sure that the people who are best at these things can keep their jobs. Sorry if this affects your service, but *shrug*