Good Practices With AE: Difference between revisions
m
no edit summary
m (another typo) |
ReikoBest2D (talk | contribs) mNo edit summary |
||
(11 intermediate revisions by 4 users not shown) | |||
Line 1:
[[Category:Guides]][[Category:Applied Energistics 2]]
Here are some good practices to respect when building your AE network:
* Always put the highest multiple of a recipe if you can, as it reduces queries for AE.
* Always prefer
*
* If you want to use
* Always make subnetworks when you'll do something that will cause a big I/O to your item and/or fluids. This way you contain the update to the subnetwork, and lookups for item/fluids are instant. For instance ores and intermediate items from ore treatment don't need to go in the main network, you should only send the end items to the main network.
* You should prefer using AE drives instead of the chests + storage
* Always prefer teleporting the AE network instead of pulling long cables.
* If you don't need interdim teleportation of your AE network, prefer using the wireless connectors, they are less laggy. (
* If you need to teleport more than 32 channels to a destination, use a subnetwork with P2P, and then teleport the subnetwork
* Don't put storage buses on drawer controllers, because it'll lag the server, especially if you have big cuboid drawer storage, because the drawer controller will have to scan the cuboid drawer storage each time there is an item I/O done by AE on it.
*Defragment your storage! A very fragmented storage with thousands of item types can cause lag spikes when the ME system must find an object through all the internal storage (item export, recipe crafting simulation, etc)
*Don't chain power your networks with quartz fiber, power usage of accross all the networks will cause network updates back and forth between them. All your networks should have their own way of being powered, ideally neutronium cells if you unlocked them in your progression.
*Don't pattern byproducts.
|