Multiple Servers on the same box queries
sutty
Join Date: 2010-08-01 Member: 73403Members
I have a very quick question, my experience with hosting game servers, or servers in general is very limited therefore the question might seem abit basic.
I'am successfully hosting a 18 man server at the moment, I would like to host another on the same box but unsure on what I need to do.
Do I need to order more ip's from my server provider, or can I host on the same ip and change the port etc? I did look on the wiki but this wasn't covered. (its probably so basic they didn't think it was needed to be said lol)
Any help will be appreciated :)
I'am successfully hosting a 18 man server at the moment, I would like to host another on the same box but unsure on what I need to do.
Do I need to order more ip's from my server provider, or can I host on the same ip and change the port etc? I did look on the wiki but this wasn't covered. (its probably so basic they didn't think it was needed to be said lol)
Any help will be appreciated :)
Comments
Seattle #1 = port 27015
Seattle #2 = port 27017
Seattle #3 = port 27019
Seattle #4 = port 27021
Also, I find it useful (though not all agree) to set the affinity of each server process to a core (or two). For example, I'm currently experimenting with settings each server to run on overlapping cores (i5 2500k with four cores):
Seattle #1 = Cores 0,1
Seattle #2 = Cores 1,2
Seattle #3 = Cores 2,3
Seattle #4 = Cores 0,3
The only other big decision is whether to split the config and install locations. Personally, I'm running four different configs off of one installation location (to make it easier to quickly update all the servers), but that's not necessarily the best solution.
if I rdp to the server and go to the following <a href="http://localhost/index.htm" target="_blank">http://localhost/index.htm</a> I get the web admin interface, what would I need to do for the second server <a href="http://localhost/index.htm%3a%70ort" target="_blank">http://localhost/index.htm:port</a>?
Thanks :)
<a href="http://localhost:81/index.html" target="_blank">http://localhost:81/index.html</a> for server on webport 81
<a href="http://localhost:82/index.html" target="_blank">http://localhost:82/index.html</a> for server on webport 82
etc
I had considered setting the affinity, although I don't think I will be hosting 4 servers as my cpu quite abit weaker than yours - intel 975x but Its held a steady 30 ticks with 18 players :)
A lot of people are saying to lock each server to a single core yet I am noticing there seems to be a slight performance improvement giving them access to two cores. Are you seeing the same results? Also have you noticed this having any effect on server stability?
By unlocking it, a process can use more than a single core, but choking it to a single core, you are reducing performance!
Please tell me this is being done for other reasons than maximising performance.
I've only seen a maximum of 2 cores used on a single server instance no matter the amount of players. I personally lock each server instance to 2 cores on my i7 as I usually see around 20-25% usage on the second core by the server. (EDIT: <a href="http://unknownworlds.com/ns2/forums/index.php?s=&showtopic=123252&view=findpost&p=2008489" target="_blank">Another guy</a> sees this too)
@AussieKid, nope no stability issues from locking to 2 cores.
I can understand locking to two cores, since the server would never (in my experience) use more than two cores. But as soon as you lock a single core only, its limiting.
<a href="http://imgur.com/6tSts" target="_blank"><img src="http://i.imgur.com/6tStsl.png" border="0" class="linked-image" /></a>
Now, here it is without any core affinity set:
<a href="http://imgur.com/fgEsV" target="_blank"><img src="http://i.imgur.com/fgEsVl.png" border="0" class="linked-image" /></a>
I can't really see any difference between them.
I know its statistics, but to be able to truly measure we need more data, player count and entity count are obviously important, but there needs to be a more scientific way of testing this, at least until server performance is no longer an issue.
What happened to ever Summit-XL?