Hello. We have a couple of game servers that has around 35 ~ 64 players average, and it started to have lag and rubber-banding issues.
It looks like nfoservers is a reliable provider so we're thinking of migrating to you guys.
Looking at your example server lists, we noticed these servers are running flawlessly:
gflgosurftimer.game.nfoservers.com : 27015
gflgmpurge.game.nfoservers.com : 27015
aod.game.nfoservers.com : 25200
netsky.game.nfoservers.com : 25200
What configurations are these servers running? We need our servers to perform it like those above.
How many cores? Are they VPS (we're thinking of VPS)? What is the CPU clockspeed?
What plan are these servers using?
-
sdoppel
- New to forums
- Posts: 3
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Sat Jan 03, 2015 3:54 pm
Re: What plan are these servers using?
Are being ran from a fully dedicated E3-1271V3 @ 3.6 GHz(4 turbo)gflgosurftimer.game.nfoservers.com : 27015
gflgmpurge.game.nfoservers.com : 27015
Is a standard server in our rental system currently running off of an E3-1270 @ 3.4 GHz(3.8 turbo)aod.game.nfoservers.com : 25200
Is also a standard server in our rental system and is being ran off of an E3-1270V3 @ 3.5 GHz(3.9 turbo)netsky.game.nfoservers.com : 25200
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
Re: What plan are these servers using?
Those 2 GFL servers have some special configurations that the standard NFO system might not implement.
NFO is the best and most reliable host for sure, which is why we choose them. If you want help configuring mega servers like the 2 GFL servers you listed, add me on steam and I can help
Source: Those are my servers!
NFO is the best and most reliable host for sure, which is why we choose them. If you want help configuring mega servers like the 2 GFL servers you listed, add me on steam and I can help
Source: Those are my servers!
Not a NFO employee
Re: What plan are these servers using?
Sorry for double post, but servers like the 2 GFL ones you listed would not be possible on a VPS. They require the absolute most CPU power(which is why they are on the newest CPU) and are only possible on the fastest dedicated servers.
Those 2 servers consistently use 150% CPU(1.5 cores) on their box.
Those 2 servers consistently use 150% CPU(1.5 cores) on their box.
Not a NFO employee
Re: What plan are these servers using?
Sorry, I just assumed that they were VPS. I just found out they also provide dedicated servers.
And hello soja! Great to see a game server owner here!!
What server configurations do you have on them for the mega servers?
And hello soja! Great to see a game server owner here!!
What server configurations do you have on them for the mega servers?
Re: What plan are these servers using?
For CS:GO you need these commands:
sv_force_transmit_players 0 - By default CS:GO transmits all player movement to all connected players. This results in tons of CPU usage. With this command, only information for players near you is sent(This is how all other valve games do it).
net_splitrate 2 - This will reduce choke for large servers.
sv_minrate 128000
sv_maxrate 0 - These are included by NFO on managed and they are an absolute MUST.
sv_max_allowed_net_graph 4 - This is necessary as a server owner. This allows you to have net_graph 4, so you can monitor your servers performance(I use net_graph 2 usually if I don't want to see the colored graph).
sv_quota_stringcmdspersecond 4 - This is just recommended. It will protect you from some forms of DoS attacks.(This command is still experimental, we have not encountered any issues with it yet though)
For GMOD:
First, TICKRATE! Tickrate needs to be set pretty low for a mega server in the source engine. For the server you linked, we run 22 tick. This is higher than most large servers(which run 16 tick), but we use the fastest CPU available so we have some room to run a higher tickrate.
sv_allowdownload 0
sv_allowupload 0 - These are set like this by default on NFO managed, but they are required to help prevent server exploits and to get rid of random lag spikes when the server searches for player sprays(This will disable sprays in your server).
net_splitpacket_maxrate 100000 - 100k is fine because to run a 95 slot server, the tickrate needs to be pretty low, preventing a lot of data being transferred to each client.
sv_minrate 100000
sv_maxrate 0 - Again, these are added by NFO managed, but these commands are absolutely necessary for a large server.
If you have any questions please let me know
sv_force_transmit_players 0 - By default CS:GO transmits all player movement to all connected players. This results in tons of CPU usage. With this command, only information for players near you is sent(This is how all other valve games do it).
net_splitrate 2 - This will reduce choke for large servers.
sv_minrate 128000
sv_maxrate 0 - These are included by NFO on managed and they are an absolute MUST.
sv_max_allowed_net_graph 4 - This is necessary as a server owner. This allows you to have net_graph 4, so you can monitor your servers performance(I use net_graph 2 usually if I don't want to see the colored graph).
sv_quota_stringcmdspersecond 4 - This is just recommended. It will protect you from some forms of DoS attacks.(This command is still experimental, we have not encountered any issues with it yet though)
For GMOD:
First, TICKRATE! Tickrate needs to be set pretty low for a mega server in the source engine. For the server you linked, we run 22 tick. This is higher than most large servers(which run 16 tick), but we use the fastest CPU available so we have some room to run a higher tickrate.
sv_allowdownload 0
sv_allowupload 0 - These are set like this by default on NFO managed, but they are required to help prevent server exploits and to get rid of random lag spikes when the server searches for player sprays(This will disable sprays in your server).
net_splitpacket_maxrate 100000 - 100k is fine because to run a 95 slot server, the tickrate needs to be pretty low, preventing a lot of data being transferred to each client.
sv_minrate 100000
sv_maxrate 0 - Again, these are added by NFO managed, but these commands are absolutely necessary for a large server.
If you have any questions please let me know
Not a NFO employee
Re: What plan are these servers using?
Thank you so much soja. You deserve a big praise. This is really helpful!!
We might have to get dedicated then. Do you think E3-1270v3 is fine for 8 CSGO servers? (all 64 players).
We might have to get dedicated then. Do you think E3-1270v3 is fine for 8 CSGO servers? (all 64 players).
Re: What plan are these servers using?
Not at all. CS:GO is a huge CPU hog, which isn't a bad thing. It does make it very expensive to run though.
This is one of our 64 slot CS:GO servers(the one you mentioned) CPU usage.
As you can see, 150% consistent CPU usage. On a 4 core/8 thread dedi, to keep CPU at acceptable usage(we try to stay below 60% at peak), you will only be able to fit 3-4 populated CS:GO servers on a box.
This is one of our 64 slot CS:GO servers(the one you mentioned) CPU usage.
As you can see, 150% consistent CPU usage. On a 4 core/8 thread dedi, to keep CPU at acceptable usage(we try to stay below 60% at peak), you will only be able to fit 3-4 populated CS:GO servers on a box.
Not a NFO employee