Kenneth Ellefsen
Assigned
Reported
Comments
See the attached melon2.JPG.
I quote: "The attempt to grow a fruit happens when the mature stem would grow again (to "phase 9") and is not already adjacent to an instance of its fruit. First one of the four sides is chosen. In Bedrock Edition, the preference is: west, east, north, south. That is, if the block to the west of the stem is available, the fruit will grow on that block. If not, the block east of the stem will be checked, and so on."
https://minecraft.gamepedia.com/Tutorials/Pumpkin_and_melon_farming#Growth_Factors
I can confirm the same. Major performance degradation after the 1.16 update on linux dedicated server. 100% load on one core with very quickly. If I run the same world, and do the same thing (running a gold farm) hosting the server on windows (The other of the two available downloads), it runs with basically "zero" cpu load.
Load on Linux (Ubuntu 20.04) Xeon quad core with HT. Thread limit set to 8 in server.properties:
[media]
Load on Window 10, on an older core i7 laptop: (same world, same server.properties and same actions done in world, same number of clients):
[media][media]
Here we see the process spread out on multiple cores, and overall uses much less cpu in total. Doing exactly the same thing, on exactly the same server and client version. Only change is server platform linux vs windows...
Server version on both platforms: bedrock-server-1.16.1.02
When I log into the (linux) server first time it actually uses multiple cores for a very short while when it's loading up, but then goes back to overloading one core and starts lagging:
[media]
FYI: Both Linux and Windows instance is running native. No VM and no container/docker.
It is easy to reproduce from the screenshots bees2 and bees3.
Same issue still in 1.16, coming soon (tm)....