Eco - English Wiki - User contributions [en]

Server Profiling

2021-07-13T10:49:56Z

Tom: compliment -> complement

[[File:In-Game Profiling Commands.png|thumb|595x595px|In-game Admin commands that can be used to invoke profiling sessions|alt=]][[File:EcoServer Profiling Menu.png|thumb|595x595px|Various profiling options as seen in Server UI (Windows only)|alt=]]The profiling tools allow [[Server|Server Owners]] and [[Admin|Admins]] to run profiling sessions to gather diagnostic data that is especially useful when server is experiencing performance problems.
You can use this generated data to complement issue reports for [[Strange Loop Games|SLG]].

'''Introduced in version 9.5.'''
==Requirements==
For profiling to work, you need 2 [https://docs.microsoft.com/en-us/dotnet/core/diagnostics/#net-core-diagnostic-global-tools .NET Core diagnostic global tools] installed on your system:
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump <code>dotnet-dump</code>] - to take memory dumps
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace <code>dotnet-trace</code>] - to profile CPU
You have to make sure both of the tools are installed globally or available on your [[wikipedia:PATH_(variable)|systems PATH]] so the server can run them.
==Memory dumps==
For when the server is consuming too much memory.

Memory dumps can be initiated by:
*As an admin, by issuing <code>/profiler dump</code> command
*Invoking <code>Profiling -> Take memory dump</code> via Server UI Menu (Windows only)
Memory dump will start the <code>dotnet-dump</code> process, taking a full snapshot of current memory as used by the server process and the file size will be proportional to that. For example, a server that is utilizing 2GB of RAM, the dump file generated will be also 2GB.
==CPU profiling==
For when the server is consuming too much CPU.

CPU profiling can be initiated by:
*As an admin, by issuing <code>/profiler cpu</code> command
*Invoking <code>Profiler -> Profile CPU</code> via Server UI Menu (Windows only)
CPU profiling will start the <code>dotnet-trace</code> process, running it for '''1 minute''', capturing everything going on with the process for the time being.
==Full profile==
Full profile will simply take memory dump followed by CPU profiling, as if they were invoked in succession.

Server Profiling

2021-07-13T10:39:20Z

Tom: Reverted comment test

[[File:In-Game Profiling Commands.png|thumb|595x595px|In-game Admin commands that can be used to invoke profiling sessions|alt=]][[File:EcoServer Profiling Menu.png|thumb|595x595px|Various profiling options as seen in Server UI (Windows only)|alt=]]The profiling tools allow [[Server|Server Owners]] and [[Admin|Admins]] to run profiling sessions to gather diagnostic data that is especially useful when server is experiencing performance problems.
You can use this generated data to compliment issue reports for [[Strange Loop Games|SLG]].

'''Introduced in version 9.5.'''

==Requirements==
For profiling to work, you need 2 [https://docs.microsoft.com/en-us/dotnet/core/diagnostics/#net-core-diagnostic-global-tools .NET Core diagnostic global tools] installed on your system:
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump <code>dotnet-dump</code>] - to take memory dumps
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace <code>dotnet-trace</code>] - to profile CPU
You have to make sure both of the tools are installed globally or available on your [[wikipedia:PATH_(variable)|systems PATH]] so the server can run them.
==Memory dumps==
For when the server is consuming too much memory.

Memory dumps can be initiated by:
*As an admin, by issuing <code>/profiler dump</code> command
*Invoking <code>Profiling -> Take memory dump</code> via Server UI Menu (Windows only)
Memory dump will start the <code>dotnet-dump</code> process, taking a full snapshot of current memory as used by the server process and the file size will be proportional to that. For example, a server that is utilizing 2GB of RAM, the dump file generated will be also 2GB.
==CPU profiling==
For when the server is consuming too much CPU.

CPU profiling can be initiated by:
*As an admin, by issuing <code>/profiler cpu</code> command
*Invoking <code>Profiler -> Profile CPU</code> via Server UI Menu (Windows only)
CPU profiling will start the <code>dotnet-trace</code> process, running it for '''1 minute''', capturing everything going on with the process for the time being.
==Full profile==
Full profile will simply take memory dump followed by CPU profiling, as if they were invoked in succession.

Server Profiling

2021-07-13T10:39:02Z

Tom: Comment test

[[File:In-Game Profiling Commands.png|thumb|595x595px|In-game Admin commands that can be used to invoke profiling sessions|alt=]][[File:EcoServer Profiling Menu.png|thumb|595x595px|Various profiling options as seen in Server UI (Windows only)|alt=]]The profiling tools allow [[Server|Server Owners]] and [[Admin|Admins]] to run profiling sessions to gather diagnostic data that is especially useful when server is experiencing performance problems.
You can use this generated data to compliment issue reports for [[Strange Loop Games|SLG]].


==Requirements==
For profiling to work, you need 2 [https://docs.microsoft.com/en-us/dotnet/core/diagnostics/#net-core-diagnostic-global-tools .NET Core diagnostic global tools] installed on your system:
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump <code>dotnet-dump</code>] - to take memory dumps
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace <code>dotnet-trace</code>] - to profile CPU
You have to make sure both of the tools are installed globally or available on your [[wikipedia:PATH_(variable)|systems PATH]] so the server can run them.
==Memory dumps==
For when the server is consuming too much memory.

Memory dumps can be initiated by:
*As an admin, by issuing <code>/profiler dump</code> command
*Invoking <code>Profiling -> Take memory dump</code> via Server UI Menu (Windows only)
Memory dump will start the <code>dotnet-dump</code> process, taking a full snapshot of current memory as used by the server process and the file size will be proportional to that. For example, a server that is utilizing 2GB of RAM, the dump file generated will be also 2GB.
==CPU profiling==
For when the server is consuming too much CPU.

CPU profiling can be initiated by:
*As an admin, by issuing <code>/profiler cpu</code> command
*Invoking <code>Profiler -> Profile CPU</code> via Server UI Menu (Windows only)
CPU profiling will start the <code>dotnet-trace</code> process, running it for '''1 minute''', capturing everything going on with the process for the time being.
==Full profile==
Full profile will simply take memory dump followed by CPU profiling, as if they were invoked in succession.

Server Profiling

2021-07-13T10:38:33Z

Tom: Basic formatting updates

[[File:In-Game Profiling Commands.png|thumb|595x595px|In-game Admin commands that can be used to invoke profiling sessions|alt=]][[File:EcoServer Profiling Menu.png|thumb|595x595px|Various profiling options as seen in Server UI (Windows only)|alt=]]The profiling tools allow [[Server|Server Owners]] and [[Admin|Admins]] to run profiling sessions to gather diagnostic data that is especially useful when server is experiencing performance problems.
You can use this generated data to compliment issue reports for [[Strange Loop Games|SLG]].

'''Introduced in version 9.5.'''
==Requirements==
For profiling to work, you need 2 [https://docs.microsoft.com/en-us/dotnet/core/diagnostics/#net-core-diagnostic-global-tools .NET Core diagnostic global tools] installed on your system:
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump <code>dotnet-dump</code>] - to take memory dumps
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace <code>dotnet-trace</code>] - to profile CPU
You have to make sure both of the tools are installed globally or available on your [[wikipedia:PATH_(variable)|systems PATH]] so the server can run them.
==Memory dumps==
For when the server is consuming too much memory.

Memory dumps can be initiated by:
*As an admin, by issuing <code>/profiler dump</code> command
*Invoking <code>Profiling -> Take memory dump</code> via Server UI Menu (Windows only)
Memory dump will start the <code>dotnet-dump</code> process, taking a full snapshot of current memory as used by the server process and the file size will be proportional to that. For example, a server that is utilizing 2GB of RAM, the dump file generated will be also 2GB.
==CPU profiling==
For when the server is consuming too much CPU.

CPU profiling can be initiated by:
*As an admin, by issuing <code>/profiler cpu</code> command
*Invoking <code>Profiler -> Profile CPU</code> via Server UI Menu (Windows only)
CPU profiling will start the <code>dotnet-trace</code> process, running it for '''1 minute''', capturing everything going on with the process for the time being.
==Full profile==
Full profile will simply take memory dump followed by CPU profiling, as if they were invoked in succession.

Server Profiling

2021-07-13T10:36:28Z

Tom: Added basic guide for using the Server Profiling tools

[[File:In-Game Profiling Commands.png|thumb|595x595px|In-game Admin commands that can be used to invoke profiling sessions|alt=]][[File:EcoServer Profiling Menu.png|thumb|595x595px|Various profiling options as seen in Server UI (Windows only)|alt=]]The profiling tools allow [[Server|Server Owners]] and [[Admin|Admins]] to run profiling sessions to gather diagnostic data that is especially useful when server is experiencing performance problems.

You can use this generated data to compliment issue reports for [[Strange Loop Games|SLG]].
'''Introduced in version 9.5.'''
==Requirements==
For profiling to work, you need 2 [https://docs.microsoft.com/en-us/dotnet/core/diagnostics/#net-core-diagnostic-global-tools .NET Core diagnostic global tools] installed on your system:
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump <code>dotnet-dump</code>] - to take memory dumps
*[https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace <code>dotnet-trace</code>] - to profile CPU
You have to make sure both of the tools are installed globally or available on your [[wikipedia:PATH_(variable)|systems PATH]] so the server can run them.
==Memory dumps==
For when the server is consuming too much memory.

Memory dumps can be initiated by:
*As an admin, by issuing <code>/profiler dump</code> command
*Invoking <code>Profiling -> Take memory dump</code> via Server UI Menu (Windows only)
Memory dump will start the <code>dotnet-dump</code> process, taking a full snapshot of current memory as used by the server process and the file size will be proportional to that. For example, a server that is utilizing 2GB of RAM, the dump file generated will be also 2GB.
==CPU profiling==
For when the server is consuming too much CPU.

CPU profiling can be initiated by:
*As an admin, by issuing <code>/profiler cpu</code> command
*Invoking <code>Profiler -> Profile CPU</code> via Server UI Menu (Windows only)
CPU profiling will start the <code>dotnet-trace</code> process, running it for '''1 minute''', capturing everything going on with the process for the time being.
==Full profile==
Full profile will simply take memory dump followed by CPU profiling, as if they were invoked in succession.

Server

2021-07-13T09:19:12Z

Tom: Added sever profiling entry to Guides.

[[File:Server_Console_0.7.0.4.jpg|Server console in Windows 10, Eco version 0.7.0.4|thumb|600px]]
A [[server]] is an [[Eco]] world that is generated by a local or remote computer. To play Eco, you must join a server or start your own. Each server is a distinct world.

Players can also configure a locally hosted server to be visible to the public on the in-game server browser. Even non-listed servers can also be found by players that know the server IP address and port.

Server administrators may configure various [[world]] attributes, such as the size of their world, rate of skill gain, and player starting conditions.

The Eco server can be run through Steam directly. Go to Library -> Tools -> Eco Server to download and launch the server. Note that the server is also included in the Steam client download, so players wishing to play single-player don't need to download the server separately.

Steam is not required to run an Eco server. The server can also be downloaded directly from the [https://play.eco Strange Loop Games website]

Since running an Eco server is demanding for computer hardware, and the server must always be running to be playable, many players choose to rent dedicated servers from hosting services.
== Server Browser ==
{{Main|Server Browser}}
An improved [[Server Browser]] was introduced in Eco Beta release 7. Clicking "New Game" in the main menu will bring it up. The browser allows players to select between several types of worlds, as well as browse all available servers.

Players can also choose to host solo or private worlds, though it is not recommended, especially for new players.
== Guides ==
* [[System Requirements]] for a server. (Located at the bottom of the page following the link)
* [[Setting Up a Server]] for a basic guide to downloading, running, and updating the server.
* [[Setting Up a Server (advanced)]] for a more detailed guide on server configuration and troubleshooting.
* [[Updating a Server]] for instructions on how to manually update a server and migrate a saved world.
* [[Server Management]] for a few basic management tips.
* [[Server Configuration]] for a guide to configuring and modding the server.
* [[Chat Commands]] for a list of admin-only commands that can be used in the game client.
* [[RCON]] for documentation on Eco's RCON support.
* [[Terrain Editor]] for documentation on how to use the server's Terrain Editor tool.
* [[Server Profiling]] for a guide on generating diagnostic data for reports when server is experiencing performance problems.
[[de:Server]]
[[Category: Guide Pages]]
[[Category: Server management| ]]