Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-97408

1.16 Update causing high CPU usage on PC

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • None
    • 1.17.10.23 Beta, 1.16.210.59 Beta, 1.16.210.50 Beta, 1.16.200.55 Beta, 1.16.200.51 Beta, 1.16.100.60 Beta, 1.16.100.58 Beta, 1.16.100.57 Beta, 1.16.100.56 Beta, 1.16.100.55 Beta, 1.16.100.54 Beta, 1.16.100.52 Beta, 1.16.21, 1.16.20, 1.16.40 Hotfix, 1.16.100.59 Beta, 1.16.100, 1.16.200, 1.16.201 Hotfix, 1.16.210, 1.16.221 Hotfix, 1.17.41 Hotfix, 1.18.10, 1.18.12 Hotfix, 1.19.0, 1.19.31 Hotfix, 1.19.41
    • Confirmed
    • Windows
    • 459107

      Ever since the release of version 1.16.0+, I have been experiencing a lot of issues with performance on my laptop. My specs are: 6 core, 12 thread intel i7 8750h @3.7-3.9ghz when charged, 32gb ram @2667mhz, and a geforce 1050ti. My CPU cache has jumped up in usage, by quite a significant factor. My laptop runs extremely hot and the fans always kick into max speed.

      Overall performance is still much worse, as noted by a myriad of other performance related bug reports spanning since 1.16.100 betas and into 1.16.200. This CPU issue seems to be related to vsync being turned on. However, capping the FPS seems to be exponentially less strenuous on my cpu, but of course that brings severe input lag (see MCPE-98861). Simply telling players to cap their framerate is not the proper solution...Minecraft Bedrock was inadvertently advertised as the version that performs better due to the compiled language and being able to run on lower-specced devices, however that no longer seems to be the case.

      ----------------------------------------------------------------------------------

      RENDER DRAGON BETA: The new render dragon engine brought back in 1.16.100.59 is worse ** for performance. As a consequence of the game auto-detecting the minimum amount of chunks the player is allowed to generate, I am forced to render no more than 32 chunks. The result is a constant 100% cpu usage when walking around generating chunks, 60-70% usage when idle, lower FPS, and a strange side effect also being that my GPU is hardly being used. This may be what is causing the issue, but I'm not sure. See 1.16.100.59_render_dragon image below. 

      ----------------------------------------------------------------------------------

      Below, I attached some images to compare how the game performs in each version. I tested version 1.14.1 (which runs good) and 1.16.20 and 1.16.40 (which runs very poorly in terms of CPU usage), respectively.  *note, I am using no resource/behavior packs in these tests.

      In the image "1.14_generating_chunks-1", my cpu usage is at 39% when generating chunks at a 16 chunk render distance and 50 particle render distance, and no anti-aliasing.
      In the image "1.16_generating_chunks", my cpu usage is at 86% when generating chunks at a 16 chunk render distance and 50 particle render distance, and no anti-aliasing. That is a massive dip in performance. Chunk loading is very slow. My cpu L3 cache is 9mb.

      The effects of this noticeable dip in performance can even be seen in instances as simple as the main menu. 

      See the screenshot "1.14_idle_in_menu.png", my cpu usage is at only 19.2% when idle in the main menu. My fans are not even audible.

      Now see the screenshot "1.16_idle_in_menu.png", my cpu usage is over double, at 42.2%. My fans kick in on the menu. Not to mention the game in just the menu  is using 73.4% of my GPU. 

      EDIT: I attached a screenshot (called "cpu_temperatures") of cpu temperature readings for each core, 1-6. Core 1 is first, core 6 is last, read them left to right. 87 C is absurd. I took this screenshot when I was idle in my own world with 16 chunk render distance. 87 C is ridiculous for a game as simple as minecraft, without any shaders or extremely high settings.

      I used to be able to turn my render distance up much higher in previous versions, but with every successive update, performance has only gotten exponentially worse.

      Overall, resources dont seem to be used effectively in this game anymore, and it mainly seems to be attributed to render dragon, and yet Mojang insists that all devices should have it. CPU usage can be way too high, but the cores are not yielding better performance. 

        1. 1.14_generating_chunks-1.png
          1.14_generating_chunks-1.png
          1.44 MB
        2. 1.14_idle_in_menu-1.png
          1.14_idle_in_menu-1.png
          130 kB
        3. 1.16_generating_chunks.png
          1.16_generating_chunks.png
          1.19 MB
        4. 1.16_idle_in_menu.png
          1.16_idle_in_menu.png
          118 kB
        5. 1.16.100.59_render_dragon.png
          1.16.100.59_render_dragon.png
          149 kB
        6. cpu_temperatures.png
          cpu_temperatures.png
          38 kB
        7. Cpu.minecraft.png
          Cpu.minecraft.png
          36 kB
        8. High CPU when moving.png
          High CPU when moving.png
          33 kB
        9. image-2020-11-19-16-52-35-052.png
          image-2020-11-19-16-52-35-052.png
          485 kB
        10. image-2021-01-14-18-12-24-593.png
          image-2021-01-14-18-12-24-593.png
          17 kB
        11. image-2021-01-14-18-12-24-658.png
          image-2021-01-14-18-12-24-658.png
          24 kB
        12. Minecraft 9_4_2020 2_06_43 PM.png
          Minecraft 9_4_2020 2_06_43 PM.png
          829 kB
        13. Minecraft Error.PNG
          Minecraft Error.PNG
          82 kB
        14. Moving causes Lag_Trim (2).mp4
          8.94 MB
        15. Screenshot (12).png
          Screenshot (12).png
          1.37 MB
        16. Screenshot (13).png
          Screenshot (13).png
          1.32 MB
        17. Screenshot (3).png
          Screenshot (3).png
          1.39 MB
        18. Screenshot (4).png
          Screenshot (4).png
          1.20 MB

            ambient ambient
            Votes:
            117 Vote for this issue
            Watchers:
            60 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: