• Saik0@lemmy.saik0.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    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.

    • p1mrx@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      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.

      • Saik0@lemmy.saik0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        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.