geforkt von Mirrors/Paper
01a13871de
Patch documentation to come Issues with the old system that are fixed now: - World generation does not scale with cpu cores effectively. - Relies on the main thread for scheduling and maintaining chunk state, dropping chunk load/generate rates at lower tps. - Unreliable prioritisation of chunk gen/load calls that block the main thread. - Shutdown logic is utterly unreliable, as it has to wait for all chunks to unload - is it guaranteed that the chunk system is in a state on shutdown that it can reliably do this? Watchdog shutdown also typically failed due to thread checks, which is now resolved. - Saving of data is not unified (i.e can save chunk data without saving entity data, poses problems for desync if shutdown is really abnormal. - Entities are not loaded with chunks. This caused quite a bit of headache for Chunk#getEntities API, but now the new chunk system loads entities with chunks so that they are ready whenever the chunk loads in. Effectively brings the behavior back to 1.16 era, but still storing entities in their own separate regionfiles. The above list is not complete. The patch documentation will complete it. New chunk system hard relies on starlight and dataconverter, and most importantly the new concurrent utilities in ConcurrentUtil. Some of the old async chunk i/o interface (i.e the old file io thread reroutes _some_ calls to the new file io thread) is kept for plugin compat reasons. It will be removed in the next major version of minecraft. The old legacy chunk system patches have been moved to the removed folder in case we need them again.
35 Zeilen
1.7 KiB
Diff
35 Zeilen
1.7 KiB
Diff
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
|
|
From: Aikar <aikar@aikar.co>
|
|
Date: Mon, 21 Dec 2020 11:01:42 -0500
|
|
Subject: [PATCH] Optimize Dynamic#get Missing Keys
|
|
|
|
get was calling toString() on every NBT object that was ever asked for an optional
|
|
key from the object to build a string for the error text.
|
|
|
|
When done on large NBT objects, this was using a ton of computation time building the
|
|
JSON representation of the NBT object.
|
|
|
|
Now we will just skip the value when 99.9999% of the time the text is never even printed.
|
|
|
|
diff --git a/src/main/java/com/mojang/serialization/Dynamic.java b/src/main/java/com/mojang/serialization/Dynamic.java
|
|
index a75d3db046dc985a03b4b870c91f41de1bd66bad..044facc9de9e8e582d7953d681c0c051578979c3 100644
|
|
--- a/src/main/java/com/mojang/serialization/Dynamic.java
|
|
+++ b/src/main/java/com/mojang/serialization/Dynamic.java
|
|
@@ -17,6 +17,7 @@ import java.util.stream.Stream;
|
|
|
|
@SuppressWarnings("unused")
|
|
public class Dynamic<T> extends DynamicLike<T> {
|
|
+ private static final boolean DEBUG_MISSING_KEYS = Boolean.getBoolean("Paper.debugDynamicMissingKeys"); // Paper
|
|
private final T value;
|
|
|
|
public Dynamic(final DynamicOps<T> ops) {
|
|
@@ -113,7 +114,7 @@ public class Dynamic<T> extends DynamicLike<T> {
|
|
return new OptionalDynamic<>(ops, ops.getMap(value).flatMap(m -> {
|
|
final T value = m.get(key);
|
|
if (value == null) {
|
|
- return DataResult.error("key missing: " + key + " in " + this.value);
|
|
+ return DataResult.error(DEBUG_MISSING_KEYS ? "key missing: " + key + " in " + this.value : "key missing: " + key); // Paper
|
|
}
|
|
return DataResult.success(new Dynamic<>(ops, value));
|
|
}));
|