You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have also written a python script for objectively benchmarking Minecraft. The server benchmark times chunkgen, while the client benchmark repeats runs deterministically and records them with Intel presentmon. If you're interested, come try it out, post benches, and/or feel free to ping me about anything else!
The text was updated successfully, but these errors were encountered:
Hey, you have a great repository and a very useful python script! There's a lot I could improve by taking the time to learn from your repository. I would like to add though that while Xverify:none is deprecated, it does still work and may be desirable.
Hey, these flags are very interesting! But there are some issues with a few of them:
XX:+AggressiveHeap
forces ParallelGC instead of G1GC. See: https://github.com/openjdk/jdk/blob/3ebe5ad2d7771ccf7710350b749d780fef91e40c/src/hotspot/share/runtime/arguments.cpp#L1687XX:+EliminateLocks
is already enabled by default in Java 17XX:GCTimeLimit
TBH, but the source describes it as this, and I'm not sure setting it to 50 is a good idea: "Limit of the proportion of time spent in GC before an OutOfMemoryError is thrown (used with GCHeapFreeLimit)" See: https://github.com/openjdk/jdk/blob/e32377e4564e636d5ebb768b9f1ead379b08f7a5/src/hotspot/share/gc/shared/gc_globals.hpp#L485I have started a repo with a similar goal, and I will almost certainly add some of these flags there and link back here: https://github.com/brucethemoose/Minecraft-Performance-Flags-Benchmarks
I have also written a python script for objectively benchmarking Minecraft. The server benchmark times chunkgen, while the client benchmark repeats runs deterministically and records them with Intel presentmon. If you're interested, come try it out, post benches, and/or feel free to ping me about anything else!
The text was updated successfully, but these errors were encountered: