The less a container can hold, the less strain on the server.

So if you have, say 300 items in a container, all those 300 will load in a big packet, which sucks some server performance. are fed from the database in real-time, essentially the more items a container holds, the heavier the load on the server for each time that inventory is loaded. Naturally more calculations are required when something happens to that vehicle (driving, getting shot at, colliding, etc.) but essentially the computing power for all these physics & ragdoll items will take a toll.įurthermore, all inventories and contents of traders, tents, vehicles, etc. All vehicles run physics-calculations in real-time 24/7 (100% all the time) this means that for every car you have on your server, the server and each client will have to run the calculations for physics on that vehicle all the time. Every client has to load and calculate ALL clan logos/custom graphicsĪnother thing to consider is the fact that there is something called ragdoll and physics in ARMA 3, basically it is a set of calculations applied to each player body, each AI-body, and each car, and for a moment, also every placed building block.

Every client has to load and calculate ALL AI movement Every client has to load ALL the vehicles Every client has to load ALL base building items

* Every client will load and have to calculate everything that occurs on your server, meaning: There are several ways for you to optimize your server-side performance to get the maximum speed out of your Epoch server (because Epoch loads so many building items, it requires even more processing power).īefore I continue there is a fundamental thing you have to know and consider when you configure your Epoch server: It's a fact that ARMA has a dated architecture that only recently received some optimizations for multiple cores and utilizing them for different purposes (multi-tasking and multi-threading).

How to install epoch arma 3