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
I moved the saves to my Desktop, i7 4930k 3.4Ghz 6 Core, 16GB RAM running windows 10 Pro. 10-15 people on playing. Core 0 (CPU Core1 Thread1 basically) shows 50-80% all other cores and threads will be negligible use. the CPU can cope with ARK and the server runs great without Lag but if I try to play another game (something other than Ark) on my desktop the server (everyone playing) and my game become laggy and unusable
This is a huge issue, I have tried with and without the use all cores option on both Machines, no different
I don't understand how servers with 120++ users can run. There isn't a single core invented that can handle that.
Do you notice what the log says? Add -log to the launch options to see how many cores ARK says it detected. When I use -useallavailablecores it just ignores it and still says 1 core.
Its possible by setting the dinospawns down and set the taming limit to a low value.
The most power of the server is used to calculate the wild and tamed dinos.
Handling 120 players isn't a problem for the servers, its the dinos and platforms which needs the most power.
Therefore you do not see many dinos on high populated servers :)
[2017.02.07-13.00.55:014][ 0]Log file open, 02/07/17 08:00:55
[2017.02.07-13.00.55:014][ 0]LogMemory: Platform Memory Stats for WindowsServer
[2017.02.07-13.00.55:014][ 0]LogMemory: Process Physical Memory: 65.28 MB used, 65.28 MB peak
[2017.02.07-13.00.55:014][ 0]LogMemory: Process Virtual Memory: 57.61 MB used, 57.74 MB peak
[2017.02.07-13.00.55:014][ 0]LogMemory: Physical Memory: 5568.22 MB used, 16304.87 MB total
[2017.02.07-13.00.55:015][ 0]LogMemory: Virtual Memory: 289.87 MB used, 134217728.00 MB total
[2017.02.07-13.00.55:459][ 0]ARK Version: 254.89
[2017.02.07-13.00.55:459][ 0]PID: 11184
[2017.02.07-13.01.16:575][ 0]Primal Game Data Took 20.41 seconds
[2017.02.07-13.01.33:090][ 0]Server Initializing with BattlEye Anti-Cheat Protection. If you do not wish to use BattlEye, please launch with -NoBattlEye
[2017.02.07-13.01.33:098][ 0]BattlEye successfully started.
[2017.02.07-13.01.55:591][ 0]Server: "Rusthelp.pw 5x XP, 7x Harvest, 10x Train" has successfully started!
[2017.02.07-13.02.01:971][ 0]Commandline: TheIsland?listen?Port=7777?QueryPort=27015?MaxPlayers=25?AllowCrateSpawnsOnTopOfStructures=True -AutoDestroyStructures -UseBattlEye -servergamelog -useallavailablecores -usecache -nosteamclient -game -server -log
[2017.02.07-13.02.01:971][ 0]Full Startup: 70.99 seconds (BP compile: 0.00 seconds)
[2017.02.07-13.02.01:972][ 0]Number of cores 6
Thats the Log startup from on my desktop. the Poweredge startup says Number of cores 4
It makes no difference if I have the -useallavailablecores on there or not. I get the same output.
Turning BattlEye off decreases startup time and memory use but has no effect on the CPU
Actually the number of Dino's makes no difference from what i have seen. I have 1 Server save thats always loaded Dino spawn rate is not changed from default. Tamed Dino's is at 10k so the number of dino's spawning and tamed remains constant until someone tames a new one. when i run the Server with only 1 or 2 people connected it runs the CPU core at about 20-30% it's not till a few people get on that the number goes up. 10 people core 0 will show about 50-60% 15 people it will show around 70% most I had on at once was 18 and it sat around 82% with all other cores at most showing 1-5% from other running processes on the computer.
The problem is not the number of Dino's, it's that the server only uses a single core of the CPU (in the case of my multi-threaded i7 it's actually a single thread so literally half a core). if it used all the cores that 80% single core use would be less than 5% across the entire CPU.
That would make a massive difference to the performance of the game and the performance of my Desktop whilst running other things alongside the server software.
That's really weird because from everything I've researched, the UE4 engine was built around multi-core support. https://answers.unrealengine.com/questions/12107/question-using-dual-cpu-pcs.html
Interesting thread here: https://steamcommunity.com/app/346110/discussions/0/530649887196630307/
I'm kind of wondering as well, maybe multi-core support is tied to DirectX on windows, and maybe that's why we only get Single core in Linux.
One thing to try, is SteamOs itself, since some of the updates I've seen for ARK target SteamOs specifically. SteamOs has Direct3D support of a sort.. https://www.extremetech.com/gaming/178276-valve-open-sources-its-directx-to-opengl-translation-software-here-come-the-steamos-and-linux-games
Anyway, attempting to run ARK on the host server showed just constant looping of:
I can agree with this. everything i read even posts on forums from Unreal Devs say it should use 2 cores. this is deliberate so people can run multiple deid=cated servers on a single box without them crossing resources.
However in practice ARK is not doing this.
And @flamboyant DirectX is not a thing here as both my machines i have tested this on are windows based using DirectX.
As a test I have changed the affinity on my DT to use ONLY cores 9 and 11 Meaning thread 2 on Core 5 and ythread 2 on core 6. I will update when i have some data.
I think this is mainly a Linux problem. Windows almost always shows 4 cores. I've never seen Linux show 4 cores on any type of setup.
I don't believe it was ever fixed. Considering ARK is out now it's effin unexcusable for the devs to be this lazy. But there you go. Busy making DLC's while jerking off to a one year old bug that makes Linux servers unworkable.
Do yourself a favor and don't run an ARK server. The resources it took to run a virtual Windows server are now better spent running a lean Rust container.