Change Details

Starting the Linux Dedicated Server with -maxMem= values significantly larger than 2047 reduces the memory available to the server process (compared to -maxMem=2047). This significantly reduces server performance and even prevents some missions from loading at all. I attached my memory usage measurements taken with -maxMem=2047 and -maxMem=4095 (which is approximately the maximum amount of memory a 32-bit user-space process can utilize when running on a 64-bit kernel). Each line is structured as follows: unix timestamp, virtual memory in MiB, reserved memory in MiB, entire process' cpu time (seconds), individual threads' cpu time (seconds). The values are measured every second from server starup until termination via #shutdown. Use proc_stat_maxmem_2047.log as reference: - After startup (no mission is loaded by default) the RSS idles at 283M during mission voting. - After a mission is loaded the RSS peaks at 1122M until the server is #shutdown. Now proc_stat_maxmem_4095.log shows reduced memory usage: - During startup the RSS peaks at 253M and drops to 137M during mission voting. - Once a mission loads the RSS peaks at 979M, but the mission fails to load (clients return to the mission voting screen). - Back to the mission voting screen the RSS idles at 711M. {F25407} {F25408}

Starting the Linux Dedicated Server with -maxMem= values significantly larger than 2047 reduces the memory available to the server process (compared to -maxMem=2047). This significantly reduces server performance and even prevents some missions from loading at all. I attached my memory usage measurements taken with -maxMem=2047 and -maxMem=4095 (which is approximately the maximum amount of memory a 32-bit user-space process can utilize when running on a 64-bit kernel). Each line is structured as follows: unix timestamp, virtual memory in MiB, reserved memory in MiB, entire process' cpu time (seconds), individual threads' cpu time (seconds). The values are measured every second from server starup until termination via #shutdown. Use proc_stat_maxmem_2047.log as reference: - After startup (no mission is loaded by default) the RSS idles at 283M during mission voting. - After a mission is loaded the RSS peaks at 1122M until the server is #shutdown. Now proc_stat_maxmem_4095.log shows reduced memory usage: - During startup the RSS peaks at 253M and drops to 137M during mission voting. - Once a mission loads the RSS peaks at 979M, but the mission fails to load (clients return to the mission voting screen). - Back to the mission voting screen the RSS idles at 711M. {F25407} {F25408}

Starting the Linux Dedicated Server with -maxMem= values significantly larger than 2047 reduces the memory available to the server process (compared to -maxMem=2047). This significantly reduces server performance and even prevents some missions from loading at all. I attached my memory usage measurements taken with -maxMem=2047 and -maxMem=4095 (which is approximately the maximum amount of memory a 32-bit user-space process can utilize when running on a 64-bit kernel). Each line is structured as follows: unix timestamp, virtual memory in MiB, reserved memory in MiB, entire process' cpu time (seconds), individual threads' cpu time (seconds). The values are measured every second from server starup until termination via #shutdown. Use proc_stat_maxmem_2047.log as reference: - After startup (no mission is loaded by default) the RSS idles at 283M during mission voting. - After a mission is loaded the RSS peaks at 1122M until the server is #shutdown. Now proc_stat_maxmem_4095.log shows reduced memory usage: - During startup the RSS peaks at 253M and drops to 137M during mission voting. - Once a mission loads the RSS peaks at 979M, but the mission fails to load (clients return to the mission voting screen). - Back to the mission voting screen the RSS idles at 711M. {F25407} {F25408}