From ec5bbdc6324f85d970d0d3b87917b76496209c4a Mon Sep 17 00:00:00 2001 From: IrishDarkshadow Date: Mon, 24 Aug 2020 21:10:35 +0100 Subject: [PATCH] Created Configuring The Server Load Manager Inside The VM (markdown) --- ...guring-The-Server-Load-Manager-Inside-The-VM.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 Configuring-The-Server-Load-Manager-Inside-The-VM.md diff --git a/Configuring-The-Server-Load-Manager-Inside-The-VM.md b/Configuring-The-Server-Load-Manager-Inside-The-VM.md new file mode 100644 index 0000000..53c4453 --- /dev/null +++ b/Configuring-The-Server-Load-Manager-Inside-The-VM.md @@ -0,0 +1,14 @@ +When the SWG server is booted up it will default to allowing as many instances as required by the player population to spin up as needed. While that is a perfect setting for servers that expect larger populations, it's not great for resource constrained local servers for either solo players or small groups. + +To allow more granular control of how many instances are permitted to spin up, a load manager has been added to the system. It will allow you to edit a cfg file and specify what level you prefer. + +The cfg file you need to edit is : **/home/swg/swg-main/exe/linux/localOptions.cfg** + +You will find an entry in that file which looks like this: **serverLoadLevel=heavy** + +To specify the level you want, set the value from these options: +1. **light** _You should use this a solo play up to a full group (8 players)._ +1. **medium** _You should use this for multiple groups (up to 4)._ +1. **heavy** _This is the default setting and is intended for having as many instances as the population requires._ + +Once you choose your setting, save your changes to the cfg file and reboot the SWG server for the new setting to take effect. \ No newline at end of file