mirror of
https://github.com/MinecraftForge/MinecraftForge.git
synced 2026-11-12 08:17:35 +00:00
Travis Watkins
e6bbcf6a3d
When a player triggers a chunk load via walking around or teleporting there is no need to stop everything and get this chunk on the main thread. The client is used to having to wait some time for this chunk and the server doesn't immediately do anything with it except send it to the player. At the same time chunk loading is the last major source of file IO that still runs on the main thread. These two facts make it possible to offload chunks loaded for this reason to another thread. However, not all parts of chunk loading can happen off the main thread. For this we use the new AsynchronousExecutor system to split chunk loading in to three pieces. The first is loading data from disk, decompressing it, and parsing it in to an NBT structure. The second piece is creating entities and tile entities in the chunk and adding them to the world, this is still done on the main thread. The third piece is informing everyone who requested a chunk load that the load is finished. For this we register callbacks and then run them on the main thread once the previous two stages are finished. There are still cases where a chunk is needed immediately and these will still trigger chunk loading entirely on the main thread. The most obvious case is plugins using the API to request a chunk load. We also must load the chunk immediately when something in the world tries to access it. In these cases we ignore any possibly pending or in progress chunk loading that is happening asynchronously as we will have the chunk loaded by the time they are finished. The hope is that overall this system will result in less CPU time and pauses due to blocking file IO on the main thread thus giving more consistent performance. Testing so far has shown that this also speeds up chunk loading client side although some of this is likely to be because we are sending less chunks at once for the client to process. Thanks for ammaraskar for help with the implementation of this feature. This commit is based off the following : Bukkit/CraftBukkit@b8fc6ab2c1 Bukkit/CraftBukkit@85f5776df2 Bukkit/CraftBukkit@0714971ca2 Bukkit/CraftBukkit@7f49722f45 Bukkit/CraftBukkit@53ad0cf1ab
*** HOW TO INSTALL *** For Mod Users: Download the latest installer from http://files.minecraftforge.net and follow instructions given by the installer. For Mod Devs: Download the latest Forge source distribution from http://files.minecraftforge.net and unzip it to a folder. Open a command prompt, navigate to the directory where you unzipped the Forge sources, and run: If you have Gradle: gradle setupDevWorkspace If you DO NOT have Gradle installed: Windows: ./gradlew.bat setupDevWorkspace MacOS/Linux: ./gradlew setupDevWorkspace If you wish to use the Eclipse IDE, run gradle eclipse instead of gradle setupDevWorkspace, or install the Gradle plugin for Eclipse and import the Forge source folder as a Gradle project. For Contributors: (Note: This assumes you have Gradle installed. If you don't, use ./gradlew(.bat) instead of gradle. Clone this repository to a folder. Open a command prompt and navigate to the folder where you cloned this repo. Run gradle setupForge to setup your development environment. To use Eclipse, point your Eclipse workspace at the eclipse folder inside the repo. Requirements (for both mod devs and contributors): You must have a JDK installed and accessible. If you do not wish to use the gradle wrapper, you can install Gradle from http://www.gradle.org/ .