Server system specs

Quote:

---

Originally Posted by das7002

Meh, I didn't say it would. Debugging symbols memory use is inversely proportional (percentage wise) to the amount of RAM the program uses on its own...

I was really only answering your question on how to get a gs without debugging info in it...

---

I know, I am answering RBB's question... http://forum.ragezone.com/6702824-post13.html

add:

&& personally I didn't think it would, but I am testing that theory anyway...

Oh well it was a nice idea.

Quote:

---

Originally Posted by 343

However, there is a method (that I would HIGHLY recommend AGAINST) in which you MAY be able to run all instances (using a single 'instance' of GS) utilizing much less ram (you may be able to get away with 8GB or even 4GB =X

If you desire to try this method start the maps in this manner from the command line (You can start the whole server from pwAdmin, then just stop the world map, leaving everything else running -- Then use the following command to start all maps):

Code:

---

./gs gs01 gs.conf gmserver.conf gsalias.conf is01 is02 is05 is06 is07 is08 is09 is10 is11 is12 is13 is14 is15 is16 is17 is18 is19 is20 is21 is22 is23 is24 is25 is26 is27 is28 is29 is31 is32 is33 is34 is35 b05 house1 house2 house3 house4 house5 house6 z9 q20 arena04 arena01 arena02 arena03 jail bg01 bg02 bg03 bg04 bg05 bg06 > /PWServer/logs/gs_all.log &

---

---

Went around and experimented with this today. In short: it does not work as you say, it's just a way to bulk load instances.

What it actually does it gs starts, fork itself and then load the specific map. It might be slightly faster to start up but it does not save any ram (as shown below). It also means once started the maps are fully independent (crash one != crash other).

Load at once (./gs 1 2)

Code:

---

$ ps -C gs -o rss,pid,ppid,command
  RSS  PID  PPID COMMAND
80668 18112 17706 ./gs gs01 gsworld.cfg gs.cfg gsworldalias.cfg is20
(few seconds later)
$ ps -C gs -o rss,pid,ppid,command
  RSS  PID  PPID COMMAND
420456 18118    1 ./gs gs01 gsworld.cfg gs.cfg gsworldalias.cfg
134024 18119    1 ./gs is20 gsworld.cfg gs.cfg gsworldalias.cfg

---

(notice the parent process becomes 1 as the initial loader dies)

Load separately (./gs 1 ; ./gs 2)

Code:

---

$ ps -C gs -o rss,pid,ppid,command
  RSS  PID  PPID COMMAND
419188 18023 17706 ./gs gs01 gsworld.cfg gs.cfg gsworldalias.cfg
133016 18052 17706 ./gs is20 gsworld.cfg gs.cfg gsworldalias.cfg

---

I will have to test that in full detail later on... All I know is that my previous tests (on my 32GB server) concluded that my release needs at least 16 GB of ram to run all maps simultaneously and safely... Also, I have never been able to open all maps at the same time on a machine with only 4GB using the 'original method'/"correct" method of loading one map at a time... However I HAVE been able to open all maps simultaneously using the above method on that same 4GB machine; I kept that server 'up' for 7 days before coming to the conclusion that it indeed does use less ram to start all the maps that way... (the server was up 7 days with no crashes)...