rates for 32man cs 1.6 server?

12114 · Post by **12114** » Sun Feb 10, 2013 12:45 pm

what do you guys think are the best rates for a cs 1.6 32 slot server, sv_minrate, sv_maxrate, sv_maxupdaterate, sv_minupdaterate wise?

i got the 1 core package with 2270 mhz, 1gb ram and whatever internet nfo has. (190/190 mbps or smth?)

12114 · Post by **12114** » Sun Feb 10, 2013 12:51 pm

why cant i edit

forgot to say: running VPS @ Windows 2008 R2

Post by **Edge100x** » Sun Feb 10, 2013 7:31 pm

Something like this should work well:

sv_minrate 30000
sv_maxrate 0
sv_minupdaterate 20
sv_maxupdaterate 120
sv_mincmdrate 20
sv_maxcmdrate 120

12114 · Post by **12114** » Mon Feb 11, 2013 5:04 am

Edge100x wrote:Something like this should work well:

sv_minrate 30000
sv_maxrate 0
sv_minupdaterate 20
sv_maxupdaterate 120
sv_mincmdrate 20
sv_maxcmdrate 120

thx, ill try it out, cause it's been lagging pretty bad lol. Every few min we'd get a 5 second freeze, and sometimes it'd give high pings out of nowhere, even though I'm only running 2x cs 1.6 servers on it (which the box should handle, and it seemed like it did because I monitored cpu usage and it didnt go over 30%)

soja · Post by **soja** » Mon Feb 11, 2013 6:34 am

Doesn't sound like a rates problem. I'm not familiar with 1.6 but if there's something equivalent to the net_splitpacket_maxrate setting for 1.6, I would try that. Otherwise it could be a plugin issue(try running a vanilla server and when the lag occurs check to see if vanilla lagged too). Otherwise maybe open a ticket with NFO to make sure the machine is running at tip-top shape.

The network connection on a NFO machine is gigabit shared (1000Mbps shared between all vds's), so random ping spikes is surely wierd, check your bandwidth graph and look for spikes, or again you can open a support ticket to see if anything out of your control is happening.

12114 · Post by **12114** » Mon Feb 11, 2013 7:25 am

soja wrote:Doesn't sound like a rates problem. I'm not familiar with 1.6 but if there's something equivalent to the net_splitpacket_maxrate setting for 1.6, I would try that. Otherwise it could be a plugin issue(try running a vanilla server and when the lag occurs check to see if vanilla lagged too). Otherwise maybe open a ticket with NFO to make sure the machine is running at tip-top shape.

The network connection on a NFO machine is gigabit shared (1000Mbps shared between all vds's), so random ping spikes is surely wierd, check your bandwidth graph and look for spikes, or again you can open a support ticket to see if anything out of your control is happening.

Yea, but the thing is, i ran an 100% identical server (i literally copy pasted everything from there) with the other host which i won't post here (to not advertise), and there was no lag. So it's probably not a plugin problem.

Hmm i checked server usage from control panel, and it does appear to have sime spikes (upload especially)

soja · Post by **soja** » Mon Feb 11, 2013 9:10 am

Something that would cause a noticeable spike would need to be in the few hundred megabit range.

12114 · Post by **12114** » Mon Feb 11, 2013 8:36 pm

still lagging after those rates, irritating as heck

every few minutes everyone would lag for about 2 seconds

heres a pic of server usage

Post by **Edge100x** » Mon Feb 11, 2013 9:06 pm

What sort of lag are you seeing exactly? We talk extensively about the different kinds and how to troubleshoot them here: http://www.nfoservers.com/forums/viewto ... =25&t=3930

soja · Post by **soja** » Mon Feb 11, 2013 9:19 pm

Would you mind adding me on steam(use my sig) and I can try to help you troubleshoot it.

12114 · Post by **12114** » Tue Feb 12, 2013 6:12 pm

@soja, added.

more detailed description:
i have 2 problems
a) for only some clients (but not limited to particular clients, can be anyone, just a percentage in the server), it gives really high pings temporarily. This happens to me included, i sometimes get 120ms @ net_graph 3, and when i'm fine i get 10ms (no it's not my internets fault because other servers are fine).
b) every 3 minutes or so, everyone (rarely with some exceptions) gets a big ping spike (400-500) because either the server freezes for 2 seconds or all the clients do...

Post by **Edge100x** » Tue Feb 12, 2013 6:19 pm

Are you testing with just one server running, stock (without plugins)? Is this a 2-core or better VDS? Are you testing with everyone disconnected from RDP? How much RAM free do you have?

Also, I recommend temporarily turning off RDP entirely as part of your testing, as I've seen it cause micro-CPU-spikes when attackers connect and try to guess passwords. On all our machines here, we lock down RDP so that only specific IPs can connect.

12114 · Post by **12114** » Tue Feb 12, 2013 6:28 pm

no I have 2 servers running, both with plugins. However i found something interesting, before i also had 2 servers (swarm & escape) but problem a) never happened. It only started happening to both servers when i replaced my zombie escape with superhero. It's very odd that problem a) started happening with swarm :O, beucase i used it for a month before with no problem, this tells me its a ram or cpu issue that superhero introduced. I haven't gotten around to testing if problem b) happens on swarm though, cuz I stopped playing that one, will try to test soon.

its a 1 core vps.

yes, testing with everyone disconnected from RDP (if by rdp you mean remote desktop), i close it down every time im done doing something and no1 else has access to it anyway.

i have about 666 mb of ram used, out of 1 gb.

edit: i just realized you were probably talking about disabling RDP in control panel... will try it.

Post by **Edge100x** » Tue Feb 12, 2013 6:52 pm

In terms of disabling RDP, I mean stopping its service or blocking TCP traffic to your IPs on port 3389. The latter might be easiest, since you can do it from the Firewall page in the control panel.

When running multiple servers, I recommend going with at least a 2-core VDS. This is because individual services often spike up and use 100% CPU briefly, such as during level loads, and that can cause serious problems for others when there is only one core available (preventing the OS from moving things around). Since you're running Windows and the 2-core option is only $10 more, upgrading might make sense if you plan to keep two or more running.

12114 · Post by **12114** » Tue Feb 12, 2013 7:07 pm

Ok i blocked it in firewall, will see if that fixes the problem. Double checked it and it worked, i wasn't able to connect to RDP anymore.

also out of curiosity

Traffic captured:

tcpdump: WARNING: vbr.23: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vbr.23, link-type EN10MB (Ethernet), capture size 96 bytes
21:06:18.984751 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:18.984920 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:18.999012 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:18.999211 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.004782 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.004926 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.018309 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.018476 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.032539 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.032727 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.037401 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.037543 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.047688 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.047854 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.056656 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.056825 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.063322 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.063461 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.081629 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.081827 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.095075 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.095287 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.099826 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.099984 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.109305 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.109467 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.116535 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.116690 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.123318 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.123444 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.138203 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.138382 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.151614 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.151781 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.162172 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.162337 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.166897 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.167055 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.181491 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.181654 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.185263 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.185395 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.200672 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.200849 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.204899 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.205038 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.210272 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.210390 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.229468 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.229633 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.231358 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.231454 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.249027 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.249182 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.251422 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.251530 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.263193 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.263373 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.270270 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.270429 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.279814 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.279983 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.291971 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.292130 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.309467 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.309627 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.312803 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.312915 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.325299 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.325462 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.330238 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.330374 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.345072 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.345289 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.354164 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.354324 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.373269 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.373420 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.373452 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.373531 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.383369 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.383583 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.392993 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.393191 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.406195 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.406382 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.411751 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.411900 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.414508 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 13
21:06:19.414522 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 13
21:06:19.431344 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.431535 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.433564 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.433661 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.450489 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
21:06:19.450683 IP 74.91.124.132.9987 > 76.106.224.42.59556: UDP, payload 80
21:06:19.452626 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 80
21:06:19.452747 IP 74.91.124.132.9987 > 173.230.173.119.1954: UDP, payload 80
21:06:19.462234 IP 76.106.224.42.59556 > 74.91.124.132.9987: UDP, payload 15
21:06:19.465284 IP 173.230.173.119.1954 > 74.91.124.132.9987: UDP, payload 80
100 packets captured
100 packets received by filter
0 packets dropped by kernel

does this look like a ddos? If not, how would it look like?

edit: Hmmm, still getting 110ms constantly.. unplayable..

Server rentals :: NFOservers.com

rates for 32man cs 1.6 server?

rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?

Re: rates for 32man cs 1.6 server?