Chunkloaders
In the recent Forgecraft2 lets plays they disabled chickenchunks in favor of railcrafts personal and world anchor, with the idea that offline players should not have too great a window to effect the performance that online players experience.
This seems difficult to manage and a variety of mods have implicit chunkloading, and other mods become defacto chunk loaders due to their mechanisim (buildcraft item ducts and EnderIO conduits can both end up locking chunks in memory that should be unloaded).
Opis should be able to show loaded chunks (And dimensions)
Computercraft
The minecraft server is single threaded. It seems that poorly performing CC lua programs can contribute to server tps problems. Is restricting CC necessary to maintaining a high server tps? How could an admin track down poorly performing CC devices?
Dimensions
Additonal dimensions could contribute to disk space usage - especially Mystcrafts "create random ages to explore for more pages" mechanic. However as I understand it, if players don't visit those ages they should not contribute to performance issues?
World Size
Vanilla servers frequently implement a world border to prevent the region data growing too large. Other than a disk space issue, is this really a performance optimization?
Server Restarts
What with various mods acting like implicit chunk loaders and other things 'getting stuck' in memory, I presume a server should have a daily scheduled restart.
Other Mods
Applied Energistics has been fingered on various forums as causing tps issues. As long as poorly performing AE systems are unloaded properly when the players are not online the issue with specific mods can be minimized I guess.
Opis must be the general way to track down poorly performing AE systems?
Other things
In previous worlds I have found that simply cramming too many sheep into an enclosed space could murder the server tps. Are there other known things to watch out for?
These are the things I am (currently) thinking about wrt a server with a low, volatile, tps.
* Are these realistic concerns?
* Is there anything else I should be looking at?
* Are there tools other than Opis that can be used?
In the recent Forgecraft2 lets plays they disabled chickenchunks in favor of railcrafts personal and world anchor, with the idea that offline players should not have too great a window to effect the performance that online players experience.
This seems difficult to manage and a variety of mods have implicit chunkloading, and other mods become defacto chunk loaders due to their mechanisim (buildcraft item ducts and EnderIO conduits can both end up locking chunks in memory that should be unloaded).
Opis should be able to show loaded chunks (And dimensions)
Computercraft
The minecraft server is single threaded. It seems that poorly performing CC lua programs can contribute to server tps problems. Is restricting CC necessary to maintaining a high server tps? How could an admin track down poorly performing CC devices?
Dimensions
Additonal dimensions could contribute to disk space usage - especially Mystcrafts "create random ages to explore for more pages" mechanic. However as I understand it, if players don't visit those ages they should not contribute to performance issues?
World Size
Vanilla servers frequently implement a world border to prevent the region data growing too large. Other than a disk space issue, is this really a performance optimization?
Server Restarts
What with various mods acting like implicit chunk loaders and other things 'getting stuck' in memory, I presume a server should have a daily scheduled restart.
Other Mods
Applied Energistics has been fingered on various forums as causing tps issues. As long as poorly performing AE systems are unloaded properly when the players are not online the issue with specific mods can be minimized I guess.
Opis must be the general way to track down poorly performing AE systems?
Other things
In previous worlds I have found that simply cramming too many sheep into an enclosed space could murder the server tps. Are there other known things to watch out for?
These are the things I am (currently) thinking about wrt a server with a low, volatile, tps.
* Are these realistic concerns?
* Is there anything else I should be looking at?
* Are there tools other than Opis that can be used?
Last edited: