md_5 d212863aa7 Implement an uber efficient network engine based on the Java NIO framework Netty. This is basically a complete rewrite of the Minecraft network engine with many distinct advantages. First and foremost, there will no longer be the horrid, and redundant case of 2, or even at times, 3 threads per a connection. Instead low level select/epoll based NIO is used. The number of threads used for network reading and writing will scale automatically to the number of cores for use on your server. In most cases this will be around 8 threads for a 4 core server, much better than the up to 1000 threads that could be in use at one time with the old engine. To facilitate asynchronous packet sending or receiving (currently only chat), a cached thread pool is kept handy. Currently this pool is unbounded, however at this stage we do not need to worry about servers being resource starved due to excessive spam or chat. ... == Plugin incompatibilities As a side effect of this change, plugins which rely on very specific implementation level details within Minecraft are broken. At this point in time, TagAPI and ProtocolLib are affected. If you are a user of ProtocolLib you are advised to update to the latest build, where full support is enabled. If you are a user of TagAPI, support has not yet been added, so you will need to install the updated ProtocolLib so that TagAPI may use its functions. == Stability The code within this commit has been very lightly tested in production (300 players for approximately 24 hours), however it is not guaranteed to be free from all bugs. If you experence weird connection behaviour, reporting the bug and steps to reproduce are advised. You are also free to downgrade to the latest recommend build, which is guaranteed to be stable. == Summary This commit provides a reduction in threads, which gives the CPU / operating system more time to allocate to the main server threads, as well as various other side benefits such as chat thread pooling and a slight reduction in latency. This commit is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported license.		2013-02-09 17:16:27 +11:00
..
0001-POM-Changes.patch	Actually use the parent pom.	2013-02-03 09:54:16 +11:00
0002-Spigot-changes.patch	Split TPS patch out correctly.	2013-02-08 17:09:51 +11:00
0003-Address-BUKKIT-3286-by-firing-the-inventory-close-ev.patch	Fix conflicts to update to latest Bukkit, yay fluff.	2013-01-20 14:52:20 +11:00
0004-Update-item-merge-logic.patch	10 years later...	2013-01-28 09:46:19 +11:00
0005-Include-NibbleArray-from-mc-dev-for-diff-visibility.patch	Update patch fluff.	2013-01-19 19:22:25 +11:00
0006-Implement-lightening-of-NibbleArrays-only-allocate-b.patch	Update patch fluff.	2013-01-19 19:22:25 +11:00
0007-Return-LOHS-to-full-operation.patch	Update patch fluff.	2013-01-19 19:22:25 +11:00
0008-Update-timeout-time-to-new-default-value.patch	Split TPS patch out correctly.	2013-02-08 17:09:51 +11:00
0009-Per-world-view-distance.patch	Update patch fluff + only record sync times.	2013-01-25 14:00:20 +11:00
0010-Fix-various-crop-growth-modifier-formula-issues.patch	10 years later...	2013-01-28 09:46:19 +11:00
0011-Add-OldChunkLoader-from-mc-dev-for-diff-visibility.patch	Mob spawning issues - 'fix'. See below for ideal reasoning from MikePrimm, however until ideal reasoning we must live with the CraftBukkit / Vanilla behaviour since this causes far too many issues.	2013-01-29 16:57:06 +11:00
0012-Fix-mcRegion-to-Anvil-conversion.patch	Mob spawning issues - 'fix'. See below for ideal reasoning from MikePrimm, however until ideal reasoning we must live with the CraftBukkit / Vanilla behaviour since this causes far too many issues.	2013-01-29 16:57:06 +11:00
0013-Update-versioning-check-to-correctly-resolve-api-ver.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0014-Optimize-packet-used-to-unload-chunks-for-the-client.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0015-Skip-entity.move-if-we-are-not-moving-anywhere.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0016-Alternate-sync-free-but-safe-chunk-reference-cache.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0017-Add-Custom-Timings-to-various-points.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0018-Better-more-flexible-itemstack-merging.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0019-Add-oreobfuscator-for-Spigot.patch	Split TPS patch out correctly.	2013-02-08 17:09:51 +11:00
0020-Reduce-number-of-LivingEntity-collision-checks.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0021-Track-Xray-timings.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0022-Only-count-entities-in-chunks-being-processed-for-th.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0023-Send-maps-a-lot-less-often-to-combat-the-lag-they-ca.patch	Send maps even less often, still causing lag. Appreciate if anyone can PR a config option for this, bit busy atm.	2013-02-06 21:08:58 +11:00
0024-Detect-remove-and-warn-about-null-tile-entities.patch	Update POM changes to individual patches.	2013-02-03 09:38:54 +11:00
0025-Tick-loop-optimization-sleep-for-as-long-as-possible.patch	Split TPS patch out correctly.	2013-02-08 17:09:51 +11:00
0026-Netty.patch	Implement an uber efficient network engine based on the Java NIO framework Netty. This is basically a complete rewrite of the Minecraft network engine with many distinct advantages. First and foremost, there will no longer be the horrid, and redundant case of 2, or even at times, 3 threads per a connection. Instead low level select/epoll based NIO is used. The number of threads used for network reading and writing will scale automatically to the number of cores for use on your server. In most cases this will be around 8 threads for a 4 core server, much better than the up to 1000 threads that could be in use at one time with the old engine. To facilitate asynchronous packet sending or receiving (currently only chat), a cached thread pool is kept handy. Currently this pool is unbounded, however at this stage we do not need to worry about servers being resource starved due to excessive spam or chat.	2013-02-09 17:16:27 +11:00