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):
[media]
The first correct one:
[media]
The second correct one:
[media]
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).
Roger Aydin
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).