Thanks dan. Your answer was very close to what we could observe.

The process eats up 100% CPU at around 24 players, which causes server's
FPS (sv on the graph) do become unstable, even red (below 15, as I believe)
at times.

We're gonna check if we can get realocated to somewhere with more
processing power per core, but I doubt that would be possible.

Many thanks for the feedbacks and hope this conversation can help someone
in the future.


_pilger


On 15 March 2014 18:56, dan <[email protected]> wrote:

> On 14/03/2014 15:01, pilger wrote:
>
>> Hey guys,
>>
>>
>> I need some guidance to see what can I get from a server like this one:
>>
>> vendor_id       : GenuineIntel
>>
>>> cpu family      : 6
>>> model           : 15
>>> model name      : Intel(R) Xeon(R) CPU           E5645  @ 2.40GHz
>>> stepping        : 1
>>> cpu MHz         : 2400.085
>>> cache size      : 12288 KB
>>>
>>>
> When I used a VPS the cpu was the limiting factor.
>
> I think it had 1gb ram, 1gb swap, 30gb disk and 1tb per month bandwidth -
> which IIRC was limited to 5 mpbs or so .
>
> The bandwidth never got close to being used.  I think I used about 1% per
> day
> so 30% at the end of the month.  Games don't use a lot of bandwidth.
>
> Latency is more important (except to Valve who seem to think connecting
> Americans to
> European servers with 250+ ping makes sense. Whoever wrote Valve's
> quickplay
> server selection code must be one hell of an artist. Maybe a descendant of
> Leonardo da Vinci?)
>
> "Gabe, I've painted the ceiling in the cafeteria"
> "Ok, but you need to write some code too"
> "I'll do quickplay...350 is a low ping, right?"
>
> 30gb was more than enough disk space and the 1gb ram was fine too.
> Running minecraft was a bigger problem in terms of ram than either TF2 or
> L4D 2.
>
> You need the virtualisation options that gives you 1gb ram, not shared, ie
> Xen and similar
> rather than openvz.
>
> Trouble is, most VPS aren't even sold on the basis of how much CPU you
> actually get
> or in a misleading way where they tell you the cpu specs of the host
> machine.
>
> That means there's generally not an option to pay more money to get more
> cpu resource.
> You can pay more and get more ram and more storage - but you don't need
> them.
>
> At which point, if the only thing you want to use the server for is TF2,
> you are usually better off renting a TF2 server from one of the providers
> - because
> you'll still be sharing resources, but you should get what you need
> without having
> to pay for stuff you don't need.
>
> The reason I got a VPS was twofold (a) I wanted to run different games
> like minecraft, tf2 etc
> and (b) I wanted my son to get some experience configuring and using linux.
>
> When he created a 6v6 team though, they just rented a TF2 server - it was
> cheaper and better than
> the VPS (albeit they only needed 12 or 13 slots)
>
> Try it and see is the best answer to your question though. Use net_graph 5
> on a client and look at the fps and sv fields
> when the server is full. On the best servers these will be a solid 66 and
> sv the lower the better.
>
> We found the sv rising as the server filled, and then the game, even
> though your ping is fine and it's running ok on your machine
> it felt a bit laggy. It depends who you get playing too. I mean, those
> 250+ pings that Valve connect across the pond
> won't know a good server from a bad one. People that typically spam across
> the map while jumping up and down
> will be happy and probably won't notice either.
>
> If you're playing 6v6 you might find it's good enough too with fewer
> players.
>
> Valve's changes a long time ago to limit to 66fps improved things.
>
> --
> Dan
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux

Reply via email to