Slashdot Mirror


BitTorrent Ponders Releasing World ISP P2P Speed Report

Mark.JUK writes "The San Francisco-based inventor of the hugely popular peer-to-peer (P2P) internet file sharing protocol BitTorrent has revealed that it is considering whether or not to release the broadband performance (speed) data for more than 9,000 ISPs around the world. The technology company claims that the data forms part of its new project, which is sadly still in the very early stages of development, but could one day give consumers a near real-time perspective of how their ISP is performing. It wouldn't just cover P2P traffic either, with BitTorrent also tracking general HTTP transfers too. BitTorrent claims that its service can, for example, display that most UK ISPs 'aggressively throttle BitTorrent traffic after 6 p.m. at night,' with speeds suddenly going 'off a cliff.' Suffice to say that such information could prove to be very useful for consumers and advocates of Net Neutrality."

18 of 156 comments (clear)

  1. Considering? by slaxative · · Score: 4, Insightful

    Consideration of performing an action is news now?

    --
    This is not the penguin you're looking for.
    1. Re:Considering? by bberens · · Score: 2

      ISPs throttling torrent traffic is detrimental to their business. It also happens to be important to a lot of tech savvy users. This is a shot off the bow to the ISPs who have been largely denying they do this stuff.

      --
      Check out my lame java blog at www.javachopshop.com
    2. Re:Considering? by chemicaldave · · Score: 2

      Consideration of performing an action is news now?

      It shouldn't be, but in this case it seems that's the case. They're just trying to gain some attention so everyone is listening when they do release the report. I don't really see why they wouldn't release this information.

    3. Re:Considering? by Draek · · Score: 2

      Not really, but the existence of the data itself is.

      --
      No problem is insoluble in all conceivable circumstances.
  2. Forget advocates how about consumers in general by RichMan · · Score: 4, Insightful

    Perhaps people would like to know tha the 10Mb/sec speed advertised by their provider is only available from 4am to 6:30am on weekdays.
    These actual usable bandwidth numbers should be general public knowledge. It would enable consumers to make valid choices and perhaps make providers do some real provisioning to support their advertised bandwidths.

    1. Re:Forget advocates how about consumers in general by Facegarden · · Score: 2

      Or it could also be interesting that your 10 Mb/s speed is available never. How would that go over?

      Reminds me of when I call places like my ISP and other companies. I always get the message "We're experiencing an unusually high volume of calls at the moment, please bear with us."

      Really, unusually high? Why does it *always* seem to be "unusually" high? I would love to set up some automated system to call these companies and see how often I get that message. I bet that even if you called every hour for weeks, you would always get that message. Seems to me that you can't call something unusual if its always the case.

      As far as bandwidth - yeah, its normally a crock of shit. Though currently I've gotten a great connection. I think my plan is only 20 or 25 Mb/s but I usually get over 30 on speed tests. This is Comcast in Silicon Valley (Campbell).
      -Taylor

      --
      Worldwide Military budgets: $2100 billion. Worldwide Space Exploration budgets: $38 billion. Really, world? Really?
    2. Re:Forget advocates how about consumers in general by Em+Adespoton · · Score: 2

      I bet that even if you called every hour for weeks, you would always get that message. Seems to me that you can't call something unusual if its always the case.

      Actually, they're usually only open from 9 to 5. Outside of these hours, you don't get the "unusually busy" message; you get the "please call back between 9 and 5" message. Since 9 to 5 is only 1/3 of a day, the volume they experience during this period is "unusually busy" compared to when they don't accept calls.

      I'm still amazed at how many places do this; it should be extremely easy in this day and age to at least record and sort messages during off-hours instead of saying "please call back during working hours, or call this number if your house has exploded". It would also lower the busy rating during work hours from "unusually" to "significantly".

  3. Dumb comment by GooberToo · · Score: 3, Insightful

    Suffice to say that such information could prove to be very useful for consumers and advocates of Net Neutrality.

    What a stupid thing to say. It doesn't offer any insight as to why bandwidth may have gone off a cliff. Net Neutrality is not the same thing as responsible QoS! Get that through you heads!

    After 6pm, Internet traffic for most ISPs goes through the roof. With it, latency and available bandwidth are typically negatively affected. With a responsible QoS, which is still fully Net Neutral, its easily possible to explain services such at BT "falling off a cliff." After all, if you give it a low priority, which reasonably it should, other users may simply be driving it "off the cliff."

    Me, like most every reasonable person in the world, certainly does not want to have You Tube, general web browsing, email, IRC, streaming music, game playing, or any of a number of other services negatively affected because Joe down the street is downloading his fifth illegal movie for the day, especially when he's likely to watch it later, or getting his next WoW update. Some things require an interactive level of performance - some others do not. BT, by definition, is a service which should receive a low priority in any QoS infrastructure.

    Net Neutrality is about ensuring company X doesn't get premier service at the expense of its competition. Its not about ensuring reasonable QoS to ISP customers. Please stop conflating the two.

    Now having said all that, there may be other things are work here, but there is nothing in the article which suggests there is anything controversial going on. As is, things are reasonably explainable with traditional usage trends and a reasonable desire to maintain a reasonable QoS to customers.

    1. Re:Dumb comment by geekoid · · Score: 2, Insightful

      I had a nice factual rebuttal, but this:
      "Me, like most every reasonable person in the world"

      Tells me you are so emotionally caught up in a perceived problem you stopped actually thinking about it.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:Dumb comment by LordLimecat · · Score: 2

      as Net Neutrality has to do with discriminating with types of data or origin of data,

      ORIGIN, NOT PROTOCOL.

      Sorry for yelling, but this is getting old. GP just got done giving a very lucid explanation of why throttling BT more than HTTP is NOT a Net Neutrality issue, and you promptly responded with (paraphrased)

      Yes but BT is being throttled more than HTTP, so its a neutrality issue

      Get this through your head-- throttling by protocol is called QoS. It is legitimate. It is not a net neutrality issue. Responsible ISPs do this.
      Throttling by source or destination address or domain is not QoS, is illegitimate, and IS a net neutrality issue.

      Finally, if you cant be arsed to read someones post and take the effort to understand it, please dont respond-- especially if you spout the same argument he just rebutted.

    3. Re:Dumb comment by idontgno · · Score: 2

      Net neutrality isn't particularly about origin, other than "origin outside of the ISP's own moneymaking sphere."

      Net neutrality is entirely about fairness of access in the face of pressure to monetize that access.... increasing the effective cost of access to content that the network provider isn't already making money on to drive traffic to its own revenue-providing offerings.

      So, origin is a big part of it. But ignoring protocol is misguided. QoS is explicitly about protocol, but it's also a convenient end-run on net neutrality if the protocol you're throttling happens to be a competitor to your own marketed content.

      Don't lose sight of that. Responsible ISPs will manage QoS for the best aggregate experience for their constituents. Fiduciarily responsible ISPs will also manage QoS for the best return on content and network investment, at the expense of access fairness and content diversity if necessary. It's this latter which is why QoS can be a network neutrality issue.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    4. Re:Dumb comment by shuz · · Score: 4, Informative

      After 6pm, Internet traffic for most ISPs goes through the roof. With it, latency and available bandwidth are typically negatively affected.

      Internet traffic tends to look like a perfect curve that starts an upward trend around 700-800 for a given timezone and increases in a consistent patterned manor until 12 noon. There is a slight dip between noon and 1300 a second peak from 1300 till 1400 and a steady decline until 2300 to midnight. The decline from midday until midnight is slower but from all my experience in web traffic I don't see an increase in traffic after 1800 compared to the rest of the day.

      --
      There is or can be built a machine that can simulate any physical object. -Church-Turing principle
  4. Release it! by grub · · Score: 2


    Why are they worried about ISP reactions? They're just (hopefully) releasing data. It isn't biased or skewed, it just is. If the data is embarrassing to an ISP, that's the ISP's problem.

    --
    Trolling is a art,
  5. UK ISPs are at the mercy of BT's infrastructure by nOw2 · · Score: 2

    display that most UK ISPs 'aggressively throttle BitTorrent traffic after 6 p.m. at night,' with speeds suddenly going 'off a cliff.'

    No, that's quite normal for some areas. It's not just BitTorrent but everything, due to oversubscription on BT's infrastructure. Right down latency, like a 12ms ping turning into a 50ms epic journey.

    1. Re:UK ISPs are at the mercy of BT's infrastructure by Em+Adespoton · · Score: 2

      Depends. You should see an undulating curve as people "log on" over time. If there's a sharp point on the bandwidth curve then it's generally a good indicator that something artificial is happening.

      Could it be possible that at 6 PM the Bittorrent QoS level gets adjusted, and for the rest of the day it's at the same level as http and rtsp? Definitely artificial, but not necessarily nefarious.

  6. Re:why? by commodore6502 · · Score: 3, Informative

    I don't understand why everyone always says "the US sucks" and "other countries are better" (or words to that effect). Is this a case of thinking the Grass is Greener on the other side of the fence?

    Because it isn't true. Here is how the US compares to other continent-spanning nations/federations. Maybe I'm biased but I don't think second place is a bad place to be:
    Mbit/s
    12.3 Russian Federation
    10.3 US
    10.0 EU
    9.3 Canada
    8.0 Australia
    5.7 Saudi Arabia
    4.8 Brazil
    3.8 China
    3.4 Mexico

    Mbit/s (EU versus US member states):
    29 Lithuania
    26 Latvia
    24 Romania
    23 Netherlands, Sweden
    18 Portugal
    17 Germany
    16 Bulgaria, Denmark
    15 DE, Belgium
    14 Luxembourg, MA, RI, VA, WA, Hungary, MD, France
    13 NY, Finland, NJ
    12 NH, MN, Estonia
    11 Austria
    10 Slovakia, Czech, UK, Spain
    8 Slovenia, Malta
    7 Poland
    6 Ireland, Georgia, Greece, Turkey
    5 Cyprus
    4 Italy
    3 Greenland

    --
    Information wants to be expensive AND wants to be free. So you have Value vs. Cheap distribution fighting each other.
  7. Re:Some throttling is needed when it come to BT by Em+Adespoton · · Score: 2

    Something I haven't heard ISPs doing, but which makes some sense to me...
    Instead of throttling services, why not throttle based on number of ports?

    Using this method the first 40 or so ports opened to the gateway will all be at a standard QoS. Ports opened after that will be throttled.

    Sure, this means that if you have bt running and then try to play an FPS, it's your FPS's ports that are going to be throttled at first, but after the current round of BT segments complete, the FPS connections will move up the queue, and it'll be the BT traffic throttled.

    You could even make separate queues for TCP, UDP, ICMP, etc. That way, your "must have it now" UDP, DNS and ICMP traffic can still get through... unless you're saturating those channels with stealth P2P traffic.

    Thoughts?