I updated to Spigot #836 earlier today. I haven't had an issues with stability whatsoever, but I did notice a large performance hit. After taking some timings, it appears the issue is tickTileEntity, specifically for Hoppers. The following timings are roughly comparable as far as duration, # of players, and # of entities. I can't rule out that more hoppers were in use in the more recent timings, but I don't think that it was the case. Version git-Spigot-789 (MC: 1.5.1): http://aikar.co/timings.php?url=5627542 12.66% 0.00% 71.337 s 0.0002 ms 298,706.52k 1.54% ** tickTileEntity 7.94% 0.01% 44.738 s 0.0037 ms 12,118.68k 0.56% ** tickTileEntity - TileEntityHopper Version git-Spigot-836 (MC: 1.5.2): http://aikar.co/timings.php?url=562721 33.53% 0.00% 218.701 s 0.0007 ms 311,018.40k 4.89% ** tickTileEntity 29.05% 0.05% 189.520 s 0.0238 ms 7,955.94k 3.14% ** tickTileEntity - TileEntityHopper Looking through recent CraftBukkit commits I noticed this: "Revert "Add delay to hopper even if it doesn't do anything." https://github.com/Bukkit/CraftBukkit/commit/218b84792dc32f0257e8bf3415ba3b47e717187f Does anyone know why that commit was reverted? Could it explain the increase in CPU usage by hoppers? Is there any chance of a Spigot feature that allows us to configure how often Hoppers tick?