Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Besides, a 50+ player server would be an unsustainable nightmare of server lag, urban sprawl of bases and people complaining about lack of resources and dinos. That's the flaw of Ark: the more on a sserver, the less viable/sustainable it becomes in terms of resources.
That said, research what server hosting sites are using and you can see how to consider things accordingly.
As for checking out hosting sites and seeing what they use, why would I replicate their setup if it gives such bad lag?
You dont want to run a server with an old core 2 duo or a core 2 quad for example.
an i7 or a Xeon at the least, though an i5 or similar should be doable.
with 16GB RAM at the least (depends on how much RAM the server is able to use though)
SSD's in my opinion have no impact on how the server performs, only for doing updates and the like, so a Performance 7200RPM HDD or SSHD should do the trick.
And seeing what server hosts use is to give you an IDEA of what should be used, thats why.
Hosts can have good hardware and still run into issues if the load becomes an issue or theres a problem with the ARK server itself.
This is absolutely false. One of the biggest causes of server lag is the write out to disk at the save interval. SSD becomes a necesity at the concurrent player base suggested by the OP. Every tame, every building, every platform is going to bloat up the base world save file. WC isn't kidding about the massive amount of data regarding legacy server save files.
If your intention is to host 50+ concurrent multiple Ark cluster, then you're going to want to budget a minimum 8gb RAM per Ark - the more the better to grow. 4GB for the base server footprint and then 200-300 MB RAM per player per Ark. More memory required to run MODs, but added memory typically goes into the base footprint and not per player.
Thank you guys for ansering my question. So cpu doesn't need to be over the top, just have fat ram and some nice ssd's (probably something mlc based for extra write endurance). If memory speeds are that much of an issue, I wonder if like 128gb of ram and using a ramdisk to load the server client from would be a good idea, and just save the ramdisk to an ssd every few hours or so.
Either way I have 16gb of ram in my server, im gonna need to at least double that lol.
No virtualized, Win10 + ark server manager + two servers, 4 cores assigned for each server.
And when a server have 50+- people playing, you can experiment some lags.
The problem it's not the CPU, or the ssd, or the gigabit conection, it's the bad optimization for this game.
My only issue that I experience is that the servers go into an initialization state or stops. Not crashing as crashing I understand.
It's a bit of work but if someone can add a solution to my problem, I would be very happy.
Thanks
SAGA
Nighty