you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 3 years ago (4 children)

Meh, it's good enough to be usable. I have 50/10 Mbps down/up and I can watch 1440p videos just fine. What do y'all use your internet for? Do you have like 5 family members watching stuff at the same time?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 14 points 3 years ago (1 child)

    The average US household has something like 2.5 people in it. It's safe to assume (statistically) that at least two of those people are old enough to consume web content unsupervised.

    Then there are edge cases that aren't quite so crazy, like 5 person households where everyone is over the age 14.

    So yeah, for one person 50/10 is likely just fine. But for the average household 100/15 is likely closer to baseline.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 14 points 3 years ago (1 child)

    With the increase in WFH and distance learning, I think up/down parity should be a priority as well. Not everything is just about your ability to consume mass-marketed entertainment.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 3 years ago* (last edited 3 years ago) (1 child)

    50/10

    good enough to be usable

    On a post about how ISPs are literally fucking us all over, overcharging for the most basic connections that are far behind other countries and all you have to say is iT’s UsAbLe lmao

    Youre advocating for the SLOWEST avg speed in the nation

    Americans are getting nearly 200 Mbps in download speed, but are you?

    https://www.allconnect.com/blog/us-internet-speeds-globally

    As of May 2023, Ookla’s Speedtest.net shows Americans are getting over 200 Mbps of download speed and about 23 Mbps of upload speed through their fixed broadband connections — good for 6th in the world for median fixed broadband speeds. Considering “fast internet speeds” are generally defined as any download speed above 100 Mbps, Americans are doing quite well by this measure.

    In fact, according to a recent Allconnect data report, 9 in 10 households can access at least 100 Mbps speeds.

    That’s an incredible improvement from just under a decade ago when the U.S. had an average download speed of just 31 Mbps. In 2013, America ranked 25th among 39 nations for broadband speed.

    Sub-100 is not good enough by most standards these days around the world. 50 is not even double the fastest speeds from TEN years ago

    We as consumers and citizens deserve better, especially as working from home continues to be a popular and realistic option and our global culture continues to be directly tied to internet culture/media/content.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 3 years ago (1 child)

    One major AAA game update will likely break your connection for hours for all intents and purposes.

    Bitrate of a 1440p youtube video is going to be around 20mpbs (±4). Your 50 down connection couldn't handle more than 2 streams. The lowest reported bitrate is 16mbps on their support page (https://support.google.com/youtube/answer/1722171?hl=en#zippy=%2Cbitrate). 50/16 = 3.125, with network overhead you'd be VERY lucky to get 3 streams going without stuttering.

    It's entirely possible that a family of 5 would run into issues if they're all home and some want to watch videos.

    My family of 4 have been Plex trained... So I mitigate a lot of these problems personally.

    But it's more likely that the 10 up breaks things even more. One person in the house uploading anything (or participating in zoom/teams/etc calls) will cripple your ability to make ANY request to the internet.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)

    One major AAA game update will likely break your connection
    One person in the house uploading anything will cripple your ability to make ANY request

    You are describing symptoms of bufferbloat, not capacity problems.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)

    You are describing symptoms of bufferbloat, not capacity problems.

    No... I'm not. Downloading a 100GB game from Steam for example will gladly eat the full 50 mbps this person claims is "usable". A 100GB download would be ~4.5 hours at full speed. With ANY amount of overhead it will be more than 5 hours.

    A download saturating the full connection is a capacity problem.

    To the second point... If you are on a zoom call and are uploading the full 10 mbps of your connection speed. You will have problems uploading requests to fulfill for download.

    Both of these are capacity problems. Not bufferbloat. Quite honestly, this capacity problem can CAUSE bufferbloat. There will be excessive queuing and packet loss.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago* (last edited 3 years ago) (1 child)

    Multi-hour downloads have been a thing since capacity was measured in kbps. If a simple TCP transfer causes excessive queueing, then the queueing algorithm is broken.

    A router with OpenWrt and luci-app-sqm can fix this problem, at least for an internet connection with a fixed speed limit.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 years ago (1 child)

    LMAO. No. This has nothing to do with a router. TCP is a "fair" protocol. https://www.geeksforgeeks.org/tcp-fairness-measures/

    How you can argue about this stuff and now even know how it works... beyond me.

    A steam download (which tends to open multiple TCP channels, thus choking other connections on a network)... That's taking 50 mbps + your youtube video that wants to take 7mbps. 50+7 = 57 which is > 50 mbps. This is literally a capacity problem.

    Once again... It would be the fact that you're using more than your actual bandwidth that you would cause excessive queueing and thus have a bufferbloat problem. But simply switching queueing mechanisms won't resolve it. especially if you're using traffic that isn't prioritized. Nor does switching queueing mechanisms mean that the problem was bufferbloat to begin with.

  • source
  • parent
  • hideshow 2 child comments