|
That
depends really on how many players you plan to host on your game port. The 20
player CS ports I run on the Hardfought server would run comfortably with a
heapsize set at 64meg (-heapsize 65536) each when full. Now, one thing to keep
in mind is this (and feel free to correct me if I'm wrong, I very well could be)
- setting the heapsize for your HL port only tells your OS to reserve that
amount for hlds.exe that the OS itself wont grab, under any circumstances... so
you gotta be a bit careful on how you set it. Say you run a server that has
384MB ram and you set your heapsize to use 256MB. You better make sure the rest
of the processes running on your box don't require more than 128meg, or your
server performance is going to suffer.
What
I've noticed on running my CS ports (this is on w2k adv. server SP2) is that on
initial startup hlds.exe will consume about 64 meg of physical memory and
roughly 122MB of virtual memory, regardless of the heapsize vale. When full with
20 players, physical memory usage will level out at about 130-135MB, give or
take a bit. Watch and see how much physical memory your game port will consume
when full - that's your key to where you should probably tell hlds to reserve
for itself. Maybe add about 8 meg for overhead.
K2
|
