aboutsummaryrefslogtreecommitdiffhomepage
path: root/Spigot-Server-Patches/0476-Set-cap-on-JDK-per-thread-native-byte-buffer-cache.patch
diff options
context:
space:
mode:
authorAikar <[email protected]>2020-08-06 22:49:50 -0400
committerDaniel Ennis <[email protected]>2020-08-06 22:55:24 -0400
commitadadf16548ad220bf178596f8b9bc0a0ffeaef19 (patch)
tree35cb9d5d115d5c46287914614d5512ed0864aca7 /Spigot-Server-Patches/0476-Set-cap-on-JDK-per-thread-native-byte-buffer-cache.patch
parent6f66fa57143ad9a48a8f812cf13acf62393aa56c (diff)
downloadPaper-adadf16548ad220bf178596f8b9bc0a0ffeaef19.tar.gz
Paper-adadf16548ad220bf178596f8b9bc0a0ffeaef19.zip
Drop syncPosition on teleportation patch
I'm not sure it was really helping, and now suspecting it might be causing issues Movement sucks
Diffstat (limited to 'Spigot-Server-Patches/0476-Set-cap-on-JDK-per-thread-native-byte-buffer-cache.patch')
-rw-r--r--Spigot-Server-Patches/0476-Set-cap-on-JDK-per-thread-native-byte-buffer-cache.patch30
1 files changed, 0 insertions, 30 deletions
diff --git a/Spigot-Server-Patches/0476-Set-cap-on-JDK-per-thread-native-byte-buffer-cache.patch b/Spigot-Server-Patches/0476-Set-cap-on-JDK-per-thread-native-byte-buffer-cache.patch
deleted file mode 100644
index 5f8b1c974c..0000000000
--- a/Spigot-Server-Patches/0476-Set-cap-on-JDK-per-thread-native-byte-buffer-cache.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
-From: Aikar <[email protected]>
-Date: Mon, 4 May 2020 01:08:56 -0400
-Subject: [PATCH] Set cap on JDK per-thread native byte buffer cache
-
-See: https://www.evanjones.ca/java-bytebuffer-leak.html
-
-This is potentially a source of lots of native memory usage.
-
-We are clearly seeing native usage upwards to 1-4GB which doesn't make sense.
-
-Region File usage fixed in previous patch should of tecnically only been somewhat
-temporary until GC finally gets it some time later, but between all the various
-plugins doing IO on various threads, this hidden detail of the JDK could be
-keeping long lived large direct buffers in cache.
-
-Set system properly at server startup if not set already to help protect from this.
-
-diff --git a/src/main/java/org/bukkit/craftbukkit/Main.java b/src/main/java/org/bukkit/craftbukkit/Main.java
-index ac8f1681d91251ff84938f94fc59db97560000d6..9dd994f8b111cec2dfa30a962db8654a68c344b1 100644
---- a/src/main/java/org/bukkit/craftbukkit/Main.java
-+++ b/src/main/java/org/bukkit/craftbukkit/Main.java
-@@ -20,6 +20,7 @@ public class Main {
-
- public static void main(String[] args) {
- // Todo: Installation script
-+ if (System.getProperty("jdk.nio.maxCachedBufferSize") == null) System.setProperty("jdk.nio.maxCachedBufferSize", "262144"); // Paper - cap per-thread NIO cache size
- OptionParser parser = new OptionParser() {
- {
- acceptsAll(asList("?", "help"), "Show the help");