Hi Chris, The CPU usage is unbelievably lower. I know there was a warning that L4D was more CPU-intensive that TF2 (not sure if that was slot-per-slot, or full-server-per-full-server), but in our experience the performance improvements have trounced that several times over. On out setup (Intel(R) Xeon(R) CPU X3210 @ 2.13GHz) a full TF2 server takes up 70% of a core. Each of our 5* L4D servers is taking up 20% maximum right now. People on freebsd and debian will probably disagree, but I'd like those changes rolled back to TF2 please :)
*Can't fork any more than 5, because for some weird reason each server listens on 3 UDP ports. If the first server is on port 27015, it also grabs ports 27020 and 27005, among others. So if we try to spawn a 6th server, it'll try to use 27020 as well, and fail. Trying to spawn an additional group of 5 sometimes works, sometimes doesn't. One thing, with the cool telnet console thing (which is cool, and will simplify some server stats generation stuff I do), the parent process listens on telnet too. This confused the hell out of us at first, as that's the one we tried to connect to, and it never says anything. I don't know if you're planning on doing something with that later on, but if so, it might be nice to output stuff to the telnet console warning noobs like me ;) I'd also prefer it if when forking, rather than specifying console port with 90## or similar, you just said 9000 and trusted that because you've specified a fork, that the port numbers will be incremented by one. Same for port numbers under forking, but I know that's been mentioned as something that's going to be changed anyway The other thing, which probably only matters at the moment when people are taking servers up and down quite often, is that it's difficult to take down a group of forked servers gracefully, as people keep joining; you end up having to kick a lot of people and I'm sure they get annoyed. What I did eventually was manually remove the master server entries from each server individually to stop them showing up on the list, then firewalled new connections to the servers. A way of telling forked servers to stop when they get to hibernation would be nice (maybe that's a use for that extra telnet console) But yeah, the general impression is overwhelmingly positive from a performance point of view. Philip Cass > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:hlds_linux- > [EMAIL PROTECTED] On Behalf Of Chris Green > Sent: 07 November 2008 17:53 > To: 'Half-Life dedicated Linux server mailing list' > Subject: Re: [hlds_linux] CPU usage > > I don't get that on my linux box (fedora core 9, 64 bit). > > What are people's perceptions so far in terms of the performance and > memory impact of hosting l4d servers, especially compared to our other > games? What numbers of full servers have people been able to host on > what hardware/os combinations? Internally, when we tried to push as > many servers as possible on 8-core xeons, we tended to run out of ram > before we ran out of CPU. > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:hlds_linux- > [EMAIL PROTECTED] On Behalf Of David A. Parker > Sent: Friday, November 07, 2008 9:30 AM > To: Half-Life dedicated Linux server mailing list > Subject: [hlds_linux] CPU usage > > Hello, > > Using "stats" in the L4D server console appears to indicate that the > CPU > usage is at 99.9%: > > CPU In Out Uptime Users FPS Players > 99.90 9098.73 33508.38 33 3 28.27 6 > > However, both mpstat and top indicate that it is hovering around 5% > used, 95% idle. How is CPU usage calculated by the game server? > > - Dave > > -- > > Dave Parker > Utica College > Integrated Information Technology Services > (315) 792-3229 > Registered Linux User #408177 > > _______________________________________________ > 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
