I'm really surprised by these numbers. I have some pretty finicky players who play competitively. I don't know for sure if it is in their head or not, but they claim they get lag with 1 game active on a whole quad 9550 box which I find hard to believe so I tend to take it with a grain of salt.
I would never dream of running 32 games per quad CPU, that is insane density imo. No offense but I find it amazing that you are getting any decent performance with the CPU's nearly maxed out, maybe you have some secret sauce in your system :) I get complaints after 25% CPU load on the box so we run all of ours under that at all times, which means 3-4 L4D's per box. They are using 6-9% cpu per game = up to about 40% of a core on newer hardware. This could be from tweaking done to the game settings. Nick Turner wrote: > We're running 8 servers per core on 5450s. 64 forks per 2 socket server. > 16GB is more than enough on Linux. > > We've had an entirely server almost full, the CPUs are nearly maxed out but > we didn't get any performance complaints. > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Milton Ngan > Sent: Thursday, October 22, 2009 10:39 AM > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] L4D2 server requirements > > CPU shouldn't be much of an issue. Each game takes on average 10-15% of a > core. There are obviously spikes that go higher. 8 player games don't > actually take much more CPU than a 1 player game because the server is doing > less AI work. > > On these servers, I have between 200-300 people playing at a time. This is > very similar to the player numbers we see when running TF servers, except we > run far fewer TF instances on the same hardware. > > Memory is still an important factor, because if you run out of RAM, then you > will swap and your games will hitch due to I/O latency. > > M. > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Midnight > [[email protected]] > Sent: Wednesday, October 21, 2009 6:26 PM > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] L4D2 server requirements > > What I'm asking is not how many can you spawn in a given amount of > memory, but how many can be actively running with players in them > without lagging? I find that I run out of CPU way before memory since > the game is a CPU hog. > > Surely you can't run 50 servers with players in them all at the same > time right? So how many can you run at the same time? How much cpu > does a full 8 player server use? > > Thanks for your input. > > > Milton Ngan wrote: > >> I can support 50 instances of L4D1 on a dual 2.5GHz Quad Core system. So if >> you only have one, then half that. That being said, I need at least 10GB of >> RAM on Linux to achieve this. >> >> Under Windows, there is no forked mode, so each instance will take up more >> memory resources. So I would estimate around 16GB would be required to do >> the same thing. On a 4GB Windows 2003 system we were supporting around 13 >> instances quite happily. >> >> So depending on how much memory you have, it could be that your limit is >> memory and not CPU. >> >> M. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Midnight >> Sent: Wednesday, October 21, 2009 5:19 PM >> To: Half-Life dedicated Linux server mailing list >> Subject: Re: [hlds_linux] L4D2 server requirements >> >> How many ACTIVE L4D servers can you guys run on a 2.5 Ghz Quad Xeon >> 1333MHz? Seems that I can only run 3-4 per box without people >> complaining about lag, that is less than 1 per core. I see each server >> using around 25-35% CPU of a core and 6-9 of the whole box. I know this >> is the linux list but I'm running Windows 2008, but I figure it should >> be basically the same. >> >> >> Craig H wrote: >> >> >>> It'll probably take a little more processing power per fork, I don't see it >>> as being that substantial of an increase. I'd be amazed if it is really >>> worth noting. >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >>> >>> >>> >>> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> >> >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
