[^2021-11-10_10.22.06 [1.16.5].png]
[^2021-11-10_10.25.58 [1.17.1].png]
[^2021-11-10_10.25.58 [1.17.1]-1.png]

21w08b: 265 FPS
21w10a: 190 FPS

21w11a profiling results:

OS: Linux (Arch) 64 bit
CPU: AMD Ryzen 1600
GPU: NVIDIA Geforce GTX 1060 3GB 460.56

Old hardware
Without F3:
21w08b: 290 FPS
21w10a: 105 FPS
1.17: 27 FPS

With F3:
21w08b: 245 FPS
21w10a: 85 FPS
1.17: 25 FPS

21w11a profiling results:

1.17 profiling results:

OS: Windows 10 Home
CPU: Intel i5 7300HQ
GPU: NVIDIA GeForce GTX 1050 Ti 461.72

 
New hardware | Taken on Oct. 9, 2021

Without F3
1.16.5: 650
21w08b: 625
21w10a: 150
21w11a: 110
1.17.1: 135

With F3
1.16.5: 475
21w08b: 470
21w10a: 120
21w11a: 95
1.17.1: 105

Profiling results (Done with F3 menu disabled)
21w11a: 

1.17.1:

System info
OS: Windows 10 Home 21H1 build 19043.1237
CPU: Ryzen 7 5800H
GPU: NVIDIA GeForce RTX 3060 Laptop GPU, 6GB VRAM, 130W TDP, Driver version 472.12, Optimus disabled via MUX switch

Note: FPS can also decrease depending on how many chunks are loaded. The longer you look at something the more chunks could get loaded, the lower your fps might become, after how many seconds should the measurements be taken? The balancing of cpu resources might have also changed a lot last snapshot, amount of chunks loaded (letter C) should also be reported.

Using F3 as required (gives less performance, but still...)

21w08b: 208 FPS
21w10a: 195 FPS

OS: Windows 10 Pro Insider Beta (21H1, Build 19043.899)

CPU: AMD Ryzen 5 1600AF @ 3.8Ghz (6C/12T, Zen+ Refresh version of the 1600) [Overclocked]
GPU: NVIDIA Geforce GTX 1660 6GB VRAM
GPU Driver Version: 461.92 (Latest as of 17/03/2021 09:27 UTC)

Additional information:
AdoptOpenJDK 15:
21w08b: 215fps
21w10a: 195fps

@zMxrek Re-extract the world and restart Minecraft.

21w08b: 276-310 FPS

21w10a: 165-178 FPS

OS: Windows 10 Pro 20H2 (Build 19042.868) 64 bit

CPU: AMD Ryzen 5 2600 (3.6GHz - 6 Cores/12 Threads)

GPU: Nvidia GTX 1070 Ti - 8GB VRAM (Driver Version: 461.92)

I created the worlds by my own with the seed of the test map (the chunks don't load correctly on the original test map on my PC)

21w08b: 180 FPS
21w10a: 130 FPS

OS: Windows 10 Home 20H2 64 bit
CPU: Intel i5 7300HQ @ 2.50GHz
GPU: NVIDIA GeForce GTX 1050 461.92

21w08b: 550 - 570
21w10a: 100 - 170 (Major Fluctuations)

OS: Windows 10 Pro 20H2 (Build 10.0.18363) x64

CPU: AMD Ryzen 7 2700X Eight-Core Processor, 3700 Mhz, 8 Core(s), 16 Logical Processors

GPU: MSI NVIDIA GeForce RTX 2070 Super TU104-410

21w08b: Hovering between 195 and 205 FPS (lowest point at garbage collection time)

21w10a: 190-200 FPS

OS: Windows 10 Pro 20H2 (10.0.19042.867) x64

CPU: Ryzen 5 3600 at stock speeds

GPU: AMD Radeon 5700 XT 8 GB (Driver version 27.20.14535.3005 AKA Adrenalin 21.2.3)

Having F3 closed makes my FPS shoot up to the high 200's.

21w08b: ≈ 130-140 FPS
21w10a: ≈ 120-130 FPS

OS: Windows 10
CPU: 8x Intel Core i7-3770 @ 3.40 GHz
GPU: GeForce GTX 1050 Ti (Driver: NVIDIA 457.30)

Laptop:

21w08b: 85 FPS
21w10a: 70 FPS

OS: MacOS Mojave 10.14.4 x64
CPU: Intel Core I7-4750HQ @ 2.00 GHz
GPU: Intel Iris Pro OpenGL Engine

Note :
GPU Noted as Intel Iris Pro 1536mb under "About This Mac"

PC:

21w08b: 160 FPS
21w10a: 120 - 130 FPS
OS: Windows 10 Home
CPU: AMD Ryzen 5 2600 Six-Core Processor
GPU: Radeon RX 580 Series - 27.20.14501.18003

Updated:

21w08b: 266 fps (at 1280 x 720, FULL SCREEN ON)

21w11a: 91 fps (at 1280 x 720, FULL SCREEN ON)

OS: MacOS Sierra 10.12.6

CPU: Intel Core i7-3770 @ 3.4 GHz

GPU: Nvidia GeForce GTX 680MX 2GB

On a side note, I tested a new test world (1280 x 720) on the latest snapshot (21w11a) and getting around 50 fps when running around, the FPS drops (around 44-50) when getting into a biome like the Tiaga biome, but when near the beach or plains biome the FPS increases (average 60).

21w11a metrics report.

Please create also a merics report and post it here!

Metrics report from 21w11a

Honestly. Since the 1.17 snapshots my whole game runs like crap. In 1.16.5 with no v-sync, no Optifine,15 chunk render distance I average at 200 fps. In the 1.17 snapshots and even worse since the OpenGL update I am struggling to even maintain 75 fps (my laptop monitor's refresh rate). Something seriously needs sorting. The game has notoriously bad optimisation as is and for it to get worse is totally unacceptable.

Intel i7 7700HQ

nVidia GTX-1070

8GB Ram

It seems that this has no affect or even improves performance on certain graphics cards. For my particular case, ignoring all prior snapshots and just comparing 21w11a and 1.16.5, I am having approximately identical performance.

21w06a severely impacted my performance, but 21w10a with OpenGL 3.2 brought it back up to par with 1.16. For some reason, 21w05b was much more optimized for my computer, and ran better than either 21w10a and 1.16.5.

Computer specs:

CPU: Dell Precision T3600 8x Intel Xeon @ 3.60 GHz
GPU: Nvidia Quadro 2000
8 GB RAM, 1 TB storage Windows 10 64-bit OS
Display: 32" Element TV, 1360x768 @ 60 Hz

1.16.5-27~43 fps while walking around
21w11a-12~24 fps while walking around

Computer specs:
CPU:4x Intel(R) Core(TM) i3-3240 CPU @3.40GHz
Geforce GT 640/PCIe/SSE2
3.2.0 NVIDIA 388.13

Hey All! Thank you for your diligent work! 

FPS in 21w08b : ~550 fps
FPS in the latest snapshot: ~108 fps
Your operating system: Windows 10 Home Version 10.0.18363 Build 18363
Your CPU: 9900k @ 4.9 
Your Graphics card: GeForce RTX 3080/PCIe/SSE2 (sorry for the flex 😉)

and driver version, as reported by the game: 3.2.0 NVIDIA 461.92
Your profiling zip file: SEE ATTACHED. (2021-03-25_16.49.29) 

– Sorry everyone, I found an error in my original report. While I properly reduced the amount of memory I was using in version 21w08b, I forgot to do so for the latest snapshot (21w11a).

I will attach another profiling.zip below. 

UPDATED FPS IN LATEST SNAPSHOT: ~105

Latest Profiling zip: 2021-03-27_15.47.39

--5/17/21--

Updating ticket because I believe the following information is pertinent: 

I had to reinstall windows recently for other reasons, completely solved my performance issues. 

21w08b: 146 FPS

21w13a: 108 FPS, 70 FPS and 29 FPS

Explanation: This turned out to be an odd one for me. Before I opened the test world in the latest snapshot, I deleted it and then re-extracted it from the Performance Test.zip, since I wanted to follow the exact steps again, as I read I had to repeat them for the latest snapshot. I then opened the freshly re-extracted test world in 21w13a and initially sat at 78-ish fps right after all chunks were loaded and then gradually stabilized to about 69-70 fps as the minutes passed. However, I decided to delete the world again, re-extract it again and open it again in the exact same snapshot just to be completely sure, because I had some tries before the first correct one (the first correct one being the one where I measured the 69-70 fps mentioned earlier) which were somewhat inconsistent with the steps (the only inconsistency I can remember was forgetting to switch to spectator mode, but there probably have been more before opening the inconsistent world), and showed a different fps probably for that reason (like 128 after the chunks were loaded, then stabilized to 104-110), but I'm not certain. But this time (the second correct one) I only measured 29-30 fps, which is quite odd given the fact that the 69-70 fps measurement was achieved by executing the same steps, so I'm not sure what's happening here, but I'm mentioning it because I'm trying to be as helpful as possible (but am probably failing horribly).

21w13a profiling results: The inconsistent one (or so I think): 

 The first correct one: 

 The second correct one: 

OS: Windows 10 Home 64-bit, version 2004 (build 19041.867)

CPU: Intel Core i7-7700HQ

GPU: NVIDIA Geforce GTX 1050 2GB 465.89

Edits:

• I followed the example comment instead of not reading it like a total idiot and writing my own slab of text with too many unnecessary attachments of which I now deleted most.

• Specified my Windows 10 version and build.

• Grammar and punctuation (hopefully I didn't miss anything).

Hi guys! Unfortunately I did not see this issue before opening mine (MC-225941) ! So I eneded up making a costum run on a benchmark world I made and I used 16 as rendering distance which underlines the problem a lot better than 12 chuncks on my system. Also I run the "benchmark" in the latest release which also uses java 16 instead of java 8.

Here I re-post my report so everything is tidy and in one place:

 
I did some testing using the integrated frametime counters inside minecraft accessible via F3 + ALT

The device specification are as follows: Core i7-8565U and Nvidia MX230, the gpu driver version is the latest up to date: 466.47, windows version is 21h1.

Testing methodology

The test was run by using a client created via the launcher based on minecraft 1.16.5 with the default java (8) and another one created in snapshot 21w20a with the default java (16.0.1). Both clients received 8 GB of allocated RAM on a system total of 16GB DDR4 running at 2400mhz CL17 running in dual channel. No applications where running in the background while running the test.

To perform the test I created a world in 1.16.5 and made a minecart railtrack to be able to standardise the logging. I let the game load all the chuncks in the track at least once after I finished building the track and then I closed the game after putting myself in the minecart in the orientation to run the benchnark and then I closed the world, I run the optimise world and made a backup of it in order to be able to re-use it for further snapshots under the same conditions. I extracted another copy and optimised it in 21w20a to convert it. At this point I started benchmarking: I waited precisely 10 seconds after being spawned in the minecarft for the fps to stabilise and I begun logging and started moving with the minecart.

Furthermore I created the same world in 21w20a with the seed (no datapack) and I made the same track and I compared the results to world in 21w20a but converted from 1.16.5, both tests on the newly generated and converted world gave the same results so they are functionally the same and I will report on the converted world for simplicity also for further snapshots in which I will use a converted from 1.16.5 world.

The settings where smooth lighting to maximum, max fps to unlimited, vsync off, render distance 16, biome blend off, particles to all, entity render distance 150 per cent, fullscreen on at 1080p, clouds on and graphics was set to fancy. Via the gamerules I locked the daylight cycle, time was set to noon, weather was set to clear and mob spawning was not allowed. No mobs or items where in the benchmark rendered area because I used carefully the kill command to get rid of everything which was spawned before I type the gamerule to disable mob spawning.

Further update in comparison to the day after I created the issue: I did the same testing also by using the iGpu (intel HUD 620) and more or less the same performance degradation in percentage is experienced like what happens with the Nvdia dGpu. I have no plans to record the iGPU runs because I use the iGPU to record the screen and so this would impact the iGPU performance run, this latter does not happen when I record the dGPU since as I said it is the iGPU to do the recording job.

For further clarification I link the private youtube video I made about the 2 of the test runs I recorded.

NOTE: the clips only contain precisely the moment the cart starts moving and they end 2 seconds after going till the end of the benchmark run. The 2 benchmarks in the video have the same amount of frames and are exactly the same lenght.)

Here is the link to the private video: [https://youtu.be/QFO4NHPXb9M]

I am reporting this because Open GL 3.2 and Java 16 where introduced to modernise the game engine and to give developers new development tools. I know that Mojang has an eye of regard about how the updates can impact performance and I also know that the changes and bugfixes made with each update can change the performance and sometimes make the game run less well but only on the surface because the bug or thing which was changed was acting in an unintended and wrong way beofore the fix. Therefore personally I am fine with the appearent impact if the appearent boost we had before was due to something not acting properly, however I still wanted this to be brought to the attention of the developers just to make sure everything is acting as they intented in the current snapshots.

I hope this feedback can be useful.

21w08b: 19-20 fps (37-47 with settings turned down)

21w20a: 14-17 fps (35-45 with settings turned down)

Might not seem like a big difference but on the new snapshots having the f3 menu or inventory open makes fps even worse than that.

OS: Windows 8.1 (64 bit)

CPU: AMD A10-5750M APU with Radeon(tm) HD Graphics

GPU: AMD Radeon HD 8650G (15.200.1062.1004)

Profiling zip file:

FPS in 21w08b: 250-290fps
FPS in 21w10a: 40-50fps
OS: Windows 10 Pro (64 bit)
CPU: 12x Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
GPU: NVIDIA GeForce GTX 1060 5GB/PCIe/SSE2 (27.21.14.6647 in device manager, 466.47 in geforce experience)
Profiling zip file:

FPS in 21w08b: 450 to 304fps
FPS in 21w10a: 40-60fps
OS: Windows 10  (64 bit)
CPU: 6x intel core i5 9400F CPU @2.90GHZ
GPU: NVIDIA RTX 2060 466.47

i found out something as well I get around 300 fps under ground then there lag is on the surface 

profiling Zip 

So since my ticket was closed as a copy for this ticket, I would like to ask my questions here:

Quick recap: I'm working on a resource pack and it worked fine in 21w18a and prior. But when 21w19a came out with the new engine the game dropped to 0-1-2 fps, and I'm keep experiencing it in 21w20a and 1.17-pre1 versions. It doesn't help if I go deep or high.
I tried out other resource packs with similar high resolution (512 pixel) and they didn't cause fps drops. So I looked for the files in my pack that do cause them and I found that animated blocks became problematic. If I have mcmeta files for block animations, which were working in 2 snapsots ago (like kelps, shiny ores, lava etc) my fps drops.

So this new engine seems weaker to me in this situation. Is there any JVM arguments I could set up in the installation to work as in the previous snapshot and full versions?
My current line is this, but I'm not technical enough to understand every part of this:

-Xmx8G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M

1.17-pre2 still has the bug.

1.17-pre3 also still has the bug

FPS in 21w08b: 84 FPS
FPS in 1.17-pre3: 49 FPS
OS: Windows 10 Pro (64 bits)
CPU: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz 1.99 GHz
GPU: Nvidia Geforce 920mx

Java: Java 16, 64Bit

FPS in 21w08b: 467

FPS in 1.17-pre3: 78

OS: Windows 10 Home 64Bit

CPU: Intel i9-10900KF

GPU: RTX 3080

^{Edit 1: I forgot to mention, this bug also causes a ton of micro-stutters. This makes the game report a MUCH higher framerate than it actually is, as these stutters effectively make the game look visually the same as about 15FPS for me in some cases.}

I want to say that the problem is not only in the smaller FPS. There are a lot of microfreezes, which sometimes make it impossible to play.

I noticed that if the "Mipmap levels" setting is set to "OFF" microfreezes almost disappear, but this does not help with FPS. I hope this will help someone.

Since nothing would make the lag stop (minimap off didn't help me, smooth lighting off, etc.) I decided to open the performance tab in the task manager.

It turns out, the newer OpenGL only uses about 7% of my GPU, whereas the original OpenGL used about 32% of it on average.
So I'm wondering if the game is capped to only use a certain percentage of the GPU, or if it really is a bug, or if it's something about the new OpenGL itself.

Something odd to note is that the GPU usage goes up once you go out of fullscreen (for me, from 7% to 11% average,) and the FPS seems a bit higher (even when the window's maximized to nearly fullscreen size,) although the stuttering is by no means gone.

Either way, I think we should also include these statistics in our comments from now on, and hopefully this issue gets fixed soon.

Don't want to be negative about how this Jira report is going, but I think that reports done are not so useful.

The report is open and has normal Mojang priority so it means they are aware this bug report exists. I think that at this point we can stop hoarding numbers of our computers for a few reasons:

• the test being done is static: standing in 1 spot and measuring the "idle" fps does not represent how the game works or how we would play. A test using a moving minecart rail would be much more usueful with a frame by frame logging and not a mere avarage at the end of the test to report here

• settings are kind of CPU bound since the res. is 720p and chunck render distance is relatively low

• some results are quite odd and I think that are due to people having some issue with video drivers which they could solve by DDUing their drivers and then clean installing them again, also some results run on old drivers despite much newer ones being available for their GPU

• what we are experiencing may partly recoverable but it is definetely not a bug since the engine has changed and also chunck culling has changed so it is debatable whether we are loosing performance or the one we got before just higher due to less accurate chunck calculations or some other bug

At the end of the day the devs have their pcs too and they can for sure test performance on theirs and get complete and more accurate and more useful data compared to the one we could ever provide here and they have all the insight needed on the game changes and game engine itself.

So I would say that since this "issue" has been noted by Mojang which is the whole point of opening this thread we can for now stop reporting numbers since they will look into it and numbers here do not help them sort this out in a better or faster way.

🙂

Amazing gaming experience since 1.17!😛

I think the problem will not be solved until the release, because there is only a week left. Method with exiting full screen is working. Before was 40-50fps, after - 65.

@Archer Legend brought up a good point about outdated drivers.

— some results are quite odd and I think that are due to people having some issue with video drivers which they could solve by DDUing their drivers and then clean installing them again, also some results run on old drivers despite much newer ones being available for their GPU"

I went to Nvidia's GeForce Experience and did a reinstall of all drivers, and 1.17 seems to now work nearly just as good as 1.16. I guess it means that manufacturers are actually the ones to blame if this really is the root of the issue, as they evidently aren't shipping out PCs with compatible drivers.
(thank you archer legend)

@unknown, we've been told by Mojang to create this bug report specifically to collect performance benchmarks, so that they can properly gauge what kind of impact the changes to OpenGL have.

Please discuss this issue further on the Reddit thread and reserve the comments section for further benchmarks.

FPS in 21w08b: ~180
FPS in 21w17a: ~132
Your operating system: macOS 11.5
Your CPU: Apple M1
Your Graphics card: Apple M1
...and driver version: 4.1 Metal - 71.6.4
Your profiling zip file:

21w08b: Around 280-300 FPS

1.17-rc2: Around 100-130 FPS

OS: Windows 10 Home

CPU: Intel i7-10870H
GPU: GeForce RTX 2070 - 16GB RAM

not allowed to update drivers and game only raly causes cpu spike after loading a world

I am not able to load the attached test world in 1.17 because loading of worlds with extended height is disabled. I want to add to this issue but I can't.

Will this get fixed

CPU goes up to 100 %

Can’t do a profile due to f3 bug

Forcing a lower framerate seemed to help me. 

Still stuttering and updated drivers

@unknown, please follow the directions in the ticket description to provide helpful diagnostic information. Any other comments or discussions should be taken to the linked subreddit thread here.

How can I open up the test world in 1.17?

@unknown, can you confirm that you downloaded the

world, and not the other one? I just double-checked and I'm able to open that version in 1.17.

I must have downloaded the wrong one. Thank you.

FPS in 1.16.5: 78-82 FPS
FPS in 1.17: 47-52 FPS
OS: Windows 10 Home Single Language
CPU: Intel Core i5-8265U CPU
Graphics card: NVIDIA GeForce MX110
Driver version: 26.21.14.4287
Profiling file:

seems to be chunk loading based not graphics 

might be [MC-162253] Lag spike when crossing certain chunk borders - Jira (mojang.com) 

dan hop, I'm quite sure that is a completely unrelated issue because:
1. This report requires you to stay in spectator mode and stay still to reproduce, therefore not crossing any chunk borders; and
2. This issue first appeared in 21w10a with the rendering changes, while the issue you linked dates back to 1.14.

I put it as in my case I think it’s that  just so people know there’s not just this bug

It’s using my Gpu fine

The bug seems to go away when I close Voicemod

I have an average of 220 FPS in version 1.16.5.
In version 1.17 I have an average of 110 FPS.
I am running Windows 10 pro.

CPU: Amd Ryzen 2600

GPU: Nvidia Geforce GTX 1050TI, driver version 466.77

Edit: With my normal minecraft settings in a flat world i have an avarage of 40 FPS with constant laggspikes to 0 FPS.
At this time multiplayer has more performance for me, and even there I have bad performance because of https://bugs.mojang.com/browse/MC-123584.

The game in singleplayer has become unplayable for me at this moment. There needs to be done something!

I dont think its weird that people are getting around 100 fps with these settings. I think most people play in normal 1080x1920 resolution. In normal 1080 resolution the amount of FPS will be lower then the 1280x720 resolution.

I Can't even open the Game past snapshot 21w10a

@Carl see MC-225505

1.16.5 Average FPS (@ the settings listed above): 595
1.17 Average FPS (@ settings listed above): 380

Windows 10 Pro

CPU: AMD Ryzen 2600

GPU: NVIDIA GeForce RTX 2070, Latest driver, 466.77

Lastest windows patch has a memory leak reducing the ram you can use

1.16.5: avg fps 120

1.17.0 and 1.17.1 rc1: avg fps 100 (83 when profiling)

Windows 10 Pro

Build 19043.1055
Windows Feature Experience Pack 120.2212.2020.0

Cpu: Intel Core i7 8565U running at base clock throught all the tests (1.8ghz)

Gpu: Nvidia geforce MX230, driver version is 466.77

FPS in 1.16.5: ~400

FPS in 1.17: ~600

OS: Windows 10 Education, Version 2004 Build 19041.1052

CPU: Ryzen 3600

Graphics: RTX 2060, Driver 466.77

^{Note: in this "benchmark" of sorts, I gained a 200 FPS increase, but when I normally play (1440p, regular world generation) I usually have over 100FPS, while in 1.17 it was consistently below 60.}

^{EDIT: I forgot to set the render distance, so these numbers are with RD set to 32 chunks. Will add 12 chunk numbers shortly.}

FPS in 1.16.5 (Render Distance 12): ~370

FPS in 1.17 (Render Distance 12): ~310

FPS in 1.16.5: ~388

FPS in 1.17: ~370

OS: Windows 10 Pro 1809

CPU: AMD Ryzen 7 3700X

GPU: Nvidia GTX 960 4GB (driver version 466.77)

If the number in front of the driver version is the OpenGL version, then it seems 1.16 is using a newer version than 1.17 for some reason. Both are using the default launch parameters & settings, as well as the same config file. Weird!

With my normal settings of 16 chunk render distance at 1080p, I'm getting constant drops to the 40fps range in my survival world, and reducing the render distance barely helps, unfortunately.

FPS in 1.16: 525

FPS in 1.17: 305

Operating system: Windows 10 Pro 21H1

Grapics card: Radeon RX 570 Series 8GB

Driver version: 27.20.1034.6

1.16.5 FPS:350
1.17 FPS: 230
Windows 10 pro
CPU: 16x AMD Ryzen 7 4800H
Graphics card:NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
3.2.0 NVIDIA 471.11

1.16.5 FPS: 657
1.17 FPS: 520
OS: Windows 10 Pro 21H1
CPU: 4x Intel Core I5-6600K @ 4.5GHz
Graphics Processor: NVIDIA GTX 1660 SUPER PCIe/SSE2
3.2.0 NVIDIA 461.09

FPS in 1.16.5 : 100+ FPS, sometimes dropped to below 60 FPS
FPS in 1.17 : Below 90 or 80 FPS
Your operating system : Windows 10 Pro (64-bit) - Version 21H1 (OS Build 19043.1081)
Your CPU : Intel(R) Core(TM) i5-6400
Your Graphics card and driver version, as reported by the game : NVIDIA Geforce GTX 1050 and Driver version 471.11

FPS in 1.16.5 -  180-200
FPS in the latest 1.17 120-175
Your operating system: Windows 10 Home 64 Bit
Your CPU AMD HD 7860
Your Graphics card and driver version, as reported by the game  AMD Radeon HD 7800 Series 27.20.21002.112

It seems I'm playing devils advocate here, with an increase in FPS:

FPS in 1.16.5: 238
FPS in the latest 1.17 release (1.17): 279
Your operating system: Windows 10 (20H2, 19042.1052)
Your CPU: AMD Ryzen 9 5900X
Your Graphics card and driver version, as reported by the game: NVIDIA GeForce RTX 3090 (466.63)
Your profiling zip file: 

Honestly, the main reason I've found this issue is because of the dramatic drop in shader performance with OptiFine. I did the above tests with the Vanilla game though of course! It looks like Vanilla performance has actually improved for me. I've seen quite a few people complaining about drops in performance on older, perhaps now unsupported hardware though. I guess for me there's nothing wrong with the base game, so I'll go ahead and hope that the final release of OptiFine improves the performance again significantly.

FPS in 1.16.5: 463

FPS in 1.17.1-rc2: 310

OS: Windows 10 21H2 19043.1081

CPU: Intel Core i7 9700F @ 3.00 GHz

GPU/GPU driver version: NVIDIA GeForce GTX 1650 (version 471.11)

Profiling ZIP: https://bugs.mojang.com/secure/attachment/422512/2021-07-05_15_06_17-PerformanceTest1_17-1_17_1-rc2.zip

FPS in 1.16.5: 742FPS
FPS in the latest 1.17 release (please specify the release version): 689FPS (1.17.1)
Your operating system: Windows 10 21H1 (Build 19043.1083)
Your CPU: Ryzen 9 5900X
Your Graphics card and driver version, as reported by the game: AMD Radeon 6900XT 21.6.2

FPS in 1.16.5 330 FPS
FPS in the latest 1.17 release (please specify the release version) 69 (nice) 1.17.1
Your operating system Windows 10 64-Bit 21H1
Your CPU Ryzen 5 2600
Your Graphics card and driver version, as reported by the game GTX 1650 471.11

Your profiling zip file

FPS in 1.16.5: ~537
FPS in 1.17.1: ~325
OS: Windows 10 Pro 20H2 (build 19042.1083)
CPU: Intel(R) Core(TM) i7-9700k CPU @ 3.60GHz
Graphics card and driver version, as reported by the game: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2, 3.2.0 NVIDIA 471.11

I'm not sure if I have included all that I need to, or what posting here will do for my lag but here's mine:

1.16.5: 362 FPS
1.17.1: 240 FPS

OS: Windows 10 Home 64-bit 20H2 19042.1110
CPU: 6x Intel Core i5-9600k CPU @ 3.70GHz
GPU: NVIDIA Geforce RTX 2070 SUPER 471.11

1.17.1 profiling results:

1.16.5: 500 FPS
1.17.1: 300 FPS

1.17.1 profiling results:

OS: Windows 10 Pro x64 - 21H1 Build 19043.1110
CPU: Intel Core i5 9600KF - OC'd @ 4.9GHz
GPU: NVIDIA Geforce GTX 1660ti 6GB - 471.11

FPS in 1.16.5 : Average of 350fps : 

FPS in the latest 1.17.1 release : Average of 220fps 

Profiling results 1.17.1 : 

Windows 10 Pro N Version 10.0.19041 Build 19041

i7 4790k stock
GTX 1080 3.2.0 Nvidia 471.11

Comment : At 1920x1080 it is much worse, less than 80fps in 1.17.1 while more than 300 in 1.16.5

1.16.5: 900 FPS

1.17.1: 300 FPS

1.17.1 profiling results:

OS: Windows 10 Home 64 bit
CPU: Intel i9 9900k @ 3.60GHz
GPU: NVIDIA GeForce RTX 2080 8GB 471.41

FPS in 1.16.5: 775
FPS in the latest 1.17 release (1.17.1): 325
Your operating system: Windows 10 x64
Your CPU: Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz 3.60 GHz
Your Graphics card and driver version, as reported by the game: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 3.2.0 NVIDIA 471.41
Your profiling zip file: 

Honestly, I have no clue what I'm doing, I'm not exactly the most techy type of person, so there might be somethings that are wrong, idk.

1.16.5: 62 FPS
1.17.1: 45 FPS

OS: Windows 10 Home 64-bit 21H1 19043.1110
CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 2.10 GHz
GPU: AMD Radeon(TM) Vega 8 Graphics

1.17.1 profiling results: 

1.16.5: 150fps

1.17.1: 114fps 

Windows 10 Home 64-bit 21H1

Ryzen 5 2600 

RX 5500xt 8GB Driver 21.7.1

^{Quite a lot more noticeable at 1920x1080 (even as low as 25 fps)}

FPS in 1.16.5: 412
FPS in the latest 1.17 release (please specify the release version): 116 (21w20a)
Your operating system: Windows 10 Enterprise LTSC Version 1809
Your CPU: Intel Core i3 9100F
Your Graphics card and driver version, as reported by the game: NVIDIA GeForce GTX 1660 SUPER version 471.11
Your profiling zip file:

On 32 render distance, i got about 30 fps in 1.16 and about 20 fps in 1.17 without optifine.

With optifine, I got 50 to 60 fps in 1.16 on 32 render distance. On 1.17, I got about 30 fps with optifine on 32 render distance.

FPS in 1.16.5: 1299
FPS in 1.17.1: 579

Windows 10 Home

Intel Core i7 9700K

NVIDIA RTX 2080 Super, Driver Version: 471.68

FPS in 1.16.5: 374

FPS in 1.17.1: 303

Windows 10 Pro

AMD Ryzen 3700X 8-Core
NVIDIA GeForce RTX 3070, Driver Version: 471.68
1.17.1 Profiling Results:

Can confirm in 21w37a, although there are other performance issues in said version.

1.16.5 - average fps = 90

1.17 - average fps = 75

Windows 10 Enterprise

Ryzen 3 2200g

Integrated GPU 😞 Radeon Vega 8 Graphics version 21.9.1

Profiling Zip File

FPS in 1.16.5 - 612
FPS in the latest 1.17.1 - 248
My operating system - Windows 10 Home
My CPU - AMD Ryzen 3 3200G
My Graphics card and driver version, as reported by the game - Nvidia GTX 1050 Ti 471.68
My profiling zip file

1.16.5

1.17.1

Can confirm in 21w38a.

Can confirm in 21w39a.

1.16.5:

High -100

Med -80

Low -30

1.17.1:

High -100

Med -50

Low -11

i5 - 5200u

Nvidia GT 920m

Can confirm 1.17 versions and recent snapshots have considerably worse performance than 1.16.5

Used to be able to have 60 fps constant and 60-40 fps with BSL shaders in 1.16.5 with 10 Chunk distance , Fancy , Entitiy range 75%

Barely 50-30~ in vanilla no mods and with Optifine / Sodium in 1.17.1 same settings as above (and with BSL shaders it's barely 20-10 fps now)

Also barely 50-30~ in 1.18 snapshots no mods (obviously) same settings as above + new rendering and simulation options don't seem to help much at all.

Aye something is definitely wrong when even Optifine or Sodium can't fix the performance issues in 1.17.1 compared to huge boost they gave in 1.16.5

I really hope this is possible to sort out without me needing to buy a new PC

Can confirm in 21w40a.

Can confirm in 21w41a.

Can Confirm!

1.16.5 – 305 FPS   (Couldn't drop Resolution to 1280x720@60hz)

1.17.1 – 98 FPS

OS: Windows 10 (x64)

CPU: Intel I7 10th-Gen 10750H 6 Cores (12 With hyperthreading)

GPU: Nvidia GeForce RTX 2060

Profiling:

Can Minecraft please deal with this? I hate how nobody is even assigned to fixing this issue.

Does resetting my pc help with this? I've heard it somewhere.

This has been an issue for months now... Have as anyone from the dev team even had a look at this forum yet ?

@unknown, as was mentioned in previous comments, this report's main purpose is to gather information. Comments that are not directly contributing helpful information should be taken to the linked subreddit. Seeing as you previously indicated your issue was resolved with updated graphics drivers (at least for 1.17), I'd recommend you provide new profiling details, along with screenshots, as per this report's instructions.

Note: I accidentally set it to 1280x768@60 instead of 1280x720@60, but the relative results should still be clear.

Average FPS in 1.16.5: 315

Average FPS in 1.17.1: 248 

1.17.1 Profiling: 

From what I've seen, the upgrade to OpenGL hasn't done too much, although it still causes some performance loss. However, it's clear that the current rendering engine can't keep up with 1.18. I loaded up the 1.17 performance world and got nearly the same results. However, when I load a world made in 1.18, the rendering engine can not keep up.

Average FPS in 21w42a with 1.17 World: roughly 150 FPS
21w42a Profiling: 

The game seems to be running smoothly- just like 1.17. Doesn't seem to be too different from 1.17.

In 1.18 worlds, the game is quite laggy in general while moving around. Staying still is fine for me, but actual gameplay comes with tons of stuttering and lag. Raising the RAM to 4GB helps, but still results in quite laggy gameplay. 

Intel [email protected]
NVIDIA GeForce RTX 3080 (Custom Dell Card for Alienware R11)
32GB of RAM at 2667 MHz
Windows 10 Home
GeForce Game Ready Driver: Version 472.12

I Also noticed a Bad Perfomance and high CPU usage on the 1.18 snapshots. 

In 1.17 I have constant 144FPS in 1440P with 10 chunks

In 1.18 I have lot of FPS drops to 120~100 and High CPU usage with same settings

Sorry i don't have the time to make a test but here are my specs :

i7 4790K

32GB Ram

RTX 2060

game on SSD

@AegisFalcon This report is for performance issues with the new OpenGL version, not 1.18 performance issues

Minecraft java 1.17.1 lags a TON! I used to average about 160fps now I get about 1-15fps! Even with optifine and sodium. I get solid 144fps in Minecraft bedrock. Please fix this.

*-16gb ram

-AMD Ryzen 3

-Vega 3 graphics*

1.16.5: 856 FPS
1.17.1: 499 FPS

1.16.5 profiling results: 

1.17.1 profiling results:

OS: Windows 10 64 bit
CPU: Intel i7-10700
GPU: NVIDIA Geforce RTX 2070 Super 4.6GB 471.35

OS: Windows 10 64-bit (10.0.19043 Build 19043)

CPU: AMD Ryzen 5 3600 (6x 3600MHz)

GPU: NVIDIA Geforce RTX 3080 10GB GDDR6X; Drivers: 496.13 released 10/12/2021

Java: Version 8 Update 311 (Build 1.80_311-b11)

Since both 1.16.5 and 1.17.1 were released after snapshot 21w10a I made an extra comparison including 1.14.1.

My ingame graphics settings are default.

1.16.5 results in "PerformanceTest1_17" world

1.17.1 results in "PerformanceTest1_17" world

As you can see there are just little differences between 1.16.5 and 1.17.1. Both are really bad results as you can see in the following comparison.

1.14.4 results in new generated world

1.16.5 results in new generated world

1.17.1 results in new generated world

Compared with the older OpenGL version from the 1.14.4 version of Minecraft the newer 1.16.5 and latest 1.17.1 are really bad.

Can confirm in 21w43a.

1.16.5: 314 fps
1.17.1: 281 fps
21w43a: 270 fps

Latest snapshot profiling: 

OS: Windows 10 Pro 64bit Build 19042
CPU: Intel Core i7 6950X (Overclocked @ 4.3GHz)
GPU: NVIDIA GeForce RTX 2080 Ti 11GB 496.13

It seems like the new snapshots are improving performance, at least for me. It seems to have fewer lag spikes.

Can confirm in 21w44a. This snapshot is significantly laggier for me than 21w43a.

Hmm for me 21w44a seems to have a little less fps problems than 21w43a (still not nearly as fps good as 1.16.5)

1.16.5: 750 FPS
1.17.1: 300 FPS

1.17.1 profiling results: 

OS: Windows 10 64 bit
CPU: 12x Intel Core i7-8700K @ 3.70GHz
GPU: NVIDIA GeForce GTX 1080/PCIe/55E2 3.2.0 NVIDIA 496.49

I was not having any issues until a few days ago.  Before I found this thread I tried several things on my own to resolve the issue including: updating video card drivers, clearing space on my HD, optimizing HD, running a full virus scan (couldn't hurt). removing all mods.  making various updates to video setting in game.  Nothing seems to help.  FPS jumps around from crazy high 800+ to crazy low 9.  

This is a very serious problem, which causes at least 60% performance loss.

Using VisualVM, I found that glBindVertexArray took up a lot of CPU time.

I think this is caused by frequent OpenGL calls after glBindVertexArray, such as glBindBuffer, glEnableVertexAttribArray, glVertexAttribPointer. 

VAO only needs to bind its attributes once, and then it does not need to bind every time it is drawn.

Finally, a large number of drawing calls will also cause performance loss. Try merging vertex buffers into one.

From r/minecraft on 1.18pre6 and 1.18pre7 (someone else's comment not my own):

"Performance in 1.18 prereleases is still abysmal because the renderer has not been improved to compensate the change in worlds, neither for the shift to GL 3.1, nor for the rather simplistic approach to vertex storage and draw calls. The renderer "worked" for for pre-GL 3 because device drivers for old GL versions are optimized around assumptions that held for compatibility contexts, but those optimizations are not present anymore because more responsibility to be efficient with GPU object usage and draw calls is shifted to the application in GL 3. No matter what you do, today's Minecraft JE rendering is severely limited by single core performance and GPU bandwidth because of the excessive draw calls and buffer property rebinding, and even high end CPUs can't provide enough headroom for that."

Still somewhat unresolved for 1.18 live release.

Performance is still really poor compared to 1.16.5

FPS in 1.16.5 - 65 fps

FPS in 21w15a - 61 fps

Windows 7 SP1 with latest updates

Intel Core i5-3450, Intel HD 2500, Build 10.18.10.5161 (latest)

My screenshots are added above as: 2021-12-02_15.52.38_1.16.5 and 2021-12-02_16.08.18_21w15a

Profile data:

1.16.5: 325 FPS

1.17.1: 220 FPS

1.18: 220 FPS

1.18 profiling results:

1.17.1 profiling results:

^{OS: WIndows 10 home}

^{CPU: Intel i7 7700HQ 2.80GHz up to 3.50GHz turbo boost}

^{GPU: NVIDIA Geforce GTX1060 6GB 490.76}

1.18
130 avg
1.17
900 avg

gpu rtx 3080

cpu i7-10700kf

os: windows 10

FPS in 1.16.5   -  7
FPS in the latest 1.18.1 release 22w03a
Windows 10
Intel i7 7700HQ
Nvidia GeForceGTX 1060 with MaxQ Design. /  3.2.0 NVIDIA  472.12 

1.16.5: 150 FPS

1.17.1: 94 FPS

1.19.1 Pre Release-4: 110 FPS

Sys Info: 
AMD Ryzen 5650U with Radeon graphics (integrated), Windows 10 Pro 64-bit

1.19.1 PR-4 Profile Data:

1.17.1:

Does this still happen in the newest version? This bug has not been updated for over a year.