Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-149396

Servers are using way too much bandwidth

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: Minecraft 1.14, Minecraft 1.14.2
    • Fix Version/s: None
    • Environment:
    • Confirmation Status:
      Unconfirmed
    • Category:
      Performance

      Description

      I've set up a server to work on a project together with my friends, and recently I did a big cleanup for the 1.14 release starting in a completely fresh world, but importing builds from the previous map with structure blocks, about a 90 of them. 

      After a while of working in that new map, a friend noticed his connection started to lag a lot, and we discovered that the server was drawing about 5,5 Mb/s with just 2 people online, resulting in an idle RX of about 3,3k on both the clients. This persisted even after multiple relogs and restarts. 

      We tried to reproduce this issue on another fresh world, with gamerules like mobspawning and random ticks off, just like the world we noticed the problem in. We loaded the same datapack, as it contained functions on tick, and started loading structures and causing a lot of block-updates with explosions and fill commands, but while the idle RX went up a bit from 50 on a completely fresh world (with the ticked functions on) to 150 after we stress-tested for a while, it wasn't even close to the 3,3k we say earlier. 

      I don't know what causes the high RX, but it might have to do with the structures. I don't think the commands are the problem, as they mostly just access scoreboards and don't change a lot of blocks.

      I really hope this can be resolved, as this makes it nearly impossible for my friend to play, as his internet connection isn't very good.

      EDIT: The problem disappeared just after making this bug-report, but I still think it should be looked into.
      EDIT 2: It reappeared, but I don't know what caused it to come back.
      EDIT 3: The problem has now been gone again for a while. Once again, we don't know what caused this.

        Attachments

        1. 2019-05-07_14.54.03.png
          2019-05-07_14.54.03.png
          596 kB
        2. 2019-05-07_15.06.12.png
          2019-05-07_15.06.12.png
          1.28 MB
        3. 2019-05-07_15.08.01.png
          2019-05-07_15.08.01.png
          2.56 MB
        4. 2019-05-10_20.35.59.png
          2019-05-10_20.35.59.png
          1.23 MB
        5. 2019-05-10_20.45.10.png
          2019-05-10_20.45.10.png
          1.01 MB
        6. 2019-07-18_19.18.33.png
          2019-07-18_19.18.33.png
          726 kB
        7. 2019-07-24_10-22-48_4 vs 7.zip
          2.75 MB
        8. 2019-09-17_19.39.50.png
          2019-09-17_19.39.50.png
          509 kB
        9. debug-report-2019-07-24_22.28.06.zip
          46 kB
        10. debug-report-2019-07-24_22.30.01.zip
          33 kB
        11. debug-report-2019-07-24_22.30.23.zip
          41 kB
        12. debug-report-2019-07-24_22.32.20.zip
          39 kB
        13. debug-report-2019-09-17_19.41.48.zip
          38 kB
        14. TNTMinigame.zip
          3.72 MB

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              MCommandguy MCommandguy
            • Votes:
              11 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated: