This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] Yeah I have noticed that it has alot todo with cs_assault, as I only get max 50fps in it, versus over 150fps on other maps.
Just for the ehck of it, I had all 32 people play on de_aztec, absolutely zero lag. Its an issue with the engine and map. Which is what I honestly thought the entire time, but i wanted to confirm it. So this does confirm it, i'm going to just keep it at 28. Things seem to be ok at 28 players. As far as using the "1.4", the srcds_i686 hopes all around all 4 logical cpus, but yes I am aware of intel's "cool" partitioning of the processors. Thanks for othe confirmation information. [EMAIL PROTECTED] wrote: >Umm...comment. > >You're actually using a 1.4 to run your server and the game engine is >choking out. We see the same FPS drops on 32 slot servers and we're running >dual core Opterons with plenty of CPU and RAM to spare. It's not the >system....it's the game engine choking on itself. We dropped all of our >servers to 24 slots and all seems to work well. Understand additionally that >we're not running Linux but the Enterprise Server of Win2k3 but am posting >here to confirm your experiences even on more powerful hardware. Based on >that you can take out of the equation all things that don't match and that >leaves only one common item.....the game engine itself. Whoever in Valve >that called it "release" quality should be fired as well as the idiot that >hired him. The game has so much eye-candy and movable objects that the >single-threaded game engine is shitting it's pants. Need proof? Fire up a >server at 32 slots and closely monitor the engine's FPS. The proof is in the >diagnostics. I seriously doubt developers at Valve use the hardware we do >and we're probably not the best as there are still 275s out there. I'd like >to know who ran the servers in Valve that supported 32 players any more than >the 24 we dropped ours down to and find out how it had done it if at all. >The engine supposedly supports 64 players and nothing coming out of Valve >using the HL2 engine is even close to capable of doing it. At least have the >responsibility to state to the public that the engine is more capable than >the games that are being coded for it and or vice versa. End result, you >can't run big servers with the HL2 engine no matter your hardware or network >settings as it's the core of the engine itself that can't handle it's >workload in a single-threaded process. Too many factors to crunch when you >have 30+ players shooting cans, throwing nades that tweak a client's visual >impression of the world, barrels that fall over with their own physics and >the list could go on for another 30 lines I'm sure. The game should be >playable FIRST....and look good second. The developers seem to have it the >wrong way around. > ></end rant> > >Ray S. > > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Jason L. >Schwab >Sent: Thursday, September 29, 2005 5:39 PM >To: [email protected] >Subject: Re: [hlds_linux] Settings suggestions for 32 player DOD:S > >This is a multi-part message in MIME format. >-- >[ Picked text/plain from multipart/alternative ] >Good question, I actually hadn't checked the load averages, i'll keep an >eye on that too. > >I know i've heard the warnings about 100 tickrate and using alot of cpu, >but I have plently of cpu! > > > >Ian mu wrote: > > > >>-- >>[ Picked text/plain from multipart/alternative ] >>I think I can recall 100tick not being recommended for 32 slot servers, >>however I'm not entirely sure of the full reasoning behind that if there is >>enough cpu available. Could it be its hitting some cap of how much data it >>can send within the maxrate? >>Just wondering is the fps dropping when you do a stats command, whats the >>"load" on the server in the top right corner of top when its laggy? >> >>On 9/29/05, Jason L. Schwab <[EMAIL PROTECTED]> wrote: >> >> >> >> >>>Ok, my srcds's by default with no one playing on them use 0% cpu, and >>>140 to 160 megs of ram. Not 64. >>> >>>I told my one 24/7 cs_assault server -heapsize 256000 and it's still >>>only using 140 megs right now, is it supposed to go ahead and hold onto >>>all 256megs, or it will just use that when it needs to? Just wondering... >>> >>>As far as what I reported earlier on cpu usage, thats on 1 of the 4 >>>logical cpus, not on the overall. The overall of the 4 is about 10 to 20%. >>> >>>I do have quite a few other srcds (6) running but there all usually 0% >>>cpu and 140megs of ram, ie doing nothing. >>> >>>-Jason >>> >>>Jason L. Schwab wrote: >>> >>> >>> >>> >>> >>>>First off, thanks everyone for the replies. >>>> >>>>I do have SMP and HP enabled, as some of you asked. >>>>I have tried 100 tickrate, versus 33 and 66, makes no difference, seems >>>>100 is best though. >>>>The machine has 2 gigs of physical DDR ram (ecc registered unbuffered) >>>> >>>>I will go ahead and try making the heapsize 256megs instead of the >>>>defaults. >>>> >>>>I'll post back the results of it running 32 players, with 256megs of >>>>heapsize under tickrate of 100. >>>> >>>>As far as disabling HT, I have considered that, I did that with the >>>>2.4.X kernel, didn't seem todo a whole lot as far as performance >>>>differences, but actually run worse honestly, I haven't tried on the 2.6 >>>>kernel, though, maybe I will. >>>> >>>>It'll be full tonight i'm sure, always is, so thanks again guys. >>>> >>>>-Jason >>>> >>>>Deacon @[dgx] wrote: >>>> >>>> >>>> >>>> >>>> >>>>>We're running two 32 player DOD servers. One on CentOS 4.x and the >>>>>other >>>>>on Fedora Core RC3. >>>>> >>>>>Here is our starup info: >>>>> >>>>>Start command (Was using heapsize of 512000, but memory never seems >>>>>to be >>>>>the issue...at least not yet. >>>>> >>>>>./srcds_run -game dod +ip x.x.x.x +port xxxxx -heapsize 256000 -dll >>>>>addons/mani_admin_plugin_i486.so -secure +maxplayers 32 +map >>>>>dod_avalanche -tickrate 100 +fps_max 600 +exec server.cfg -autoupdate >>>>>-pidfile dod.pid & > /dev/null >>>>> >>>>>Crontab >>>>>*/5 * * * * renice -5 `cat /<doddir>/dod/dod.pid` >/dev/null 2>&1 >>>>> >>>>> >>>>>With the server at 31/32 (reserved slot empty) we have the following: >>>>>PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >>>>>26219 dod1 10 -5 176m 107m 9484 S 81.2 10.8 25:09.27 srcds_amd >>>>> >>>>>We never seem to have memory issues... just CPU issues. >>>>> >>>>>We're running our servers on AMD 3000+ Barton Procs w/ 1 GB RAM and 1 >>>>> >>>>> >>>>> >>>>> >>>80 >>> >>> >>> >>> >>>>>GB 10K RPM HDD. We have one server using 100 mbps eth int and the other >>>>>using 10 mbps eth int. Using 10 or 100 mbps ints doesn't seem to make a >>>>>difference. >>>>> >>>>>Here is our server.cfg. Any suggestions on how to improve our >>>>>performance? >>>>> >>>>>//----------------------------------------------- >>>>>// Server Hostname >>>>>//----------------------------------------------- >>>>> >>>>>// hostname "Customer Name - Maintenance" >>>>>hostname "Customer Name" >>>>> >>>>>//----------------------------------------------- >>>>>// Server Location >>>>>//----------------------------------------------- >>>>> >>>>>sv_lan 0 // Change it to 1 if you want a LAN only >>>>>Server >>>>>sv_region 1 // contact & geo 0=US East , 1=US West, 2= >>>>>S. America, 3=Europe, 4=Asia, 5=Australia, 6=Middle East, 7=Africa and >>>>>255=world. >>>>>sv_contact "" // Server contact name / url / email >>>>> >>>>>//----------------------------------------------- >>>>>// Server Passwords >>>>>//----------------------------------------------- >>>>> >>>>>rcon_password "" //Sets RCON Password for >>>>>server >>>>>// sv_password "" //Sets public/private >>>>>password >>>>>//sv_spectator_password "" //Sets Spectator Password >>>>>sv_rcon_minfailures 2 // # of failures needed before ban >>>>>sv_rcon_minfailuretime 600 // amount of time (seconds) failed >>>>>rcon attempts must occur within for the ban to be applied >>>>>sv_rcon_banpenalty 300 // minutes to ban. 300 = 5 hours. >>>>>sv_rcon_maxfailures 4 // similar to sv_rcon_minfailures, >>>>>Any IP that fails 3 rcon authentications >>>>> >>>>>//----------------------------------------------- >>>>>// Server Physics >>>>>//----------------------------------------------- >>>>> >>>>>sv_rollangle 0 >>>>>mp_facefronttime 600 >>>>>mp_flashlight 1 >>>>>sv_turbophysics 0 // (Default 0) >>>>>sv_stopspeed 100 // Minimum stopping speed when on ground >>>>>(default >>>>>100) >>>>>sv_friction 4 // world friction (default 4) >>>>>sv_gravity 800 // world gravity (default 800) >>>>>sv_waterfriction 1 // world water friction (default 1) >>>>>sv_accelerate 10 // (Deault 10) >>>>>sv_airaccelerate 10 // (Deault 10) >>>>>sv_wateraccelerate 10 // (Deault 10) >>>>>sv_maxspeed 320 // max player speed (default 320) >>>>>sv_stepsize 18 // player stepsize - dont mess with this >>>>>(default >>>>>18) >>>>> >>>>>//----------------------------------------------- >>>>>// Server Time & Play Limits >>>>>//----------------------------------------------- >>>>> >>>>>mp_winlimit 0 // Number of captures before map restart >>>>>mp_friendlyfire 0 // 1= On 0 = Off >>>>>mp_timelimit 45 // 30 minutes a map >>>>>mp_fraglimit 180 // set fraglimit before mapchange (Default 0) >>>>>//mp_warmup_time 30 // 30 seconds of warmup time (aka insult time) >>>>>mp_autocrosshair 0 // 1= On 0 = Off >>>>>mp_flashlight 1 // 1= On 0 = Off >>>>>mp_allowNPCs 0 // 1= On 0 = Off - allow bots >>>>>sv_alltalk 0 // teamplay talk all (1) or team only (0) >>>>>sv_voiceenable 1 // enable voice on server >>>>>sv_pausable 0 // disable pause on server (set this to 0 >>>>>always) >>>>>sv_cheats 0 // disable cheats (set this to 0 always) >>>>>sv_allowupload 0 // allow players to upload sprays (default 1) >>>>>sv_allowdownload 1 // allow sprays and map content to be downloaded >>>>>(default 1) >>>>>decalfrequency 30 // how often players can spray tags (default 10) >>>>>mapcyclefile mapcycle.txt // map cycle for this server >>>>>mp_chattime 15 // amount of seconds players can chat after the >>>>>game is over >>>>>motdfile "motd.txt" // The MOTD file to load >>>>>sv_downloadurl "" // Web Location for high speed map >>>>>downloads >>>>> >>>>>//----------------------------------------------- >>>>>// Server Player Limits >>>>>//----------------------------------------------- >>>>> >>>>>mp_autoteambalance 1 // 1= On 0 = Off >>>>>mp_limitteams 1 // Sets the number of players a team my be >>>>>unbalanced by. Set 0 to disable. >>>>>mp_forcecamera 0 // 1= On 0 = Off >>>>>mp_allowspectators 1 // 1= On 0 = Off >>>>>sv_noclipaccelerate 5 // (Default 5) >>>>>sv_noclipspeed 5 // (Default 5) >>>>>sv_specaccelerate 5 // (Default 5) >>>>>sv_specspeed 3 // (Default 3) >>>>>sv_specnoclip 1 // (Default 1) >>>>> >>>>>//----------------------------------------------- >>>>>// Server Weapon Limits >>>>>//----------------------------------------------- >>>>> >>>>>mp_weaponstay 1 // 1 = On 0 = Off >>>>>mp_limit_allies_assault 32 >>>>>mp_limit_allies_mg 2 >>>>>mp_limit_allies_rifleman 32 >>>>>mp_limit_allies_rocket 1 >>>>>mp_limit_allies_sniper 3 >>>>>mp_limit_allies_support 32 >>>>>mp_limit_axis_assault 32 >>>>>mp_limit_axis_mg 2 >>>>>mp_limit_axis_rifleman 32 >>>>>mp_limit_axis_rocket 1 >>>>>mp_limit_axis_sniper 3 >>>>>mp_limit_axis_support 32 >>>>> >>>>>//----------------------------------------------- >>>>>// Server Performance Variables >>>>>//----------------------------------------------- >>>>> >>>>>sv_instancebaselines 0 // Enable instanced baselines - Saves >>>>>network overhead (Default 1) >>>>>sv_forcepreload 1 //Force server side preloading >>>>>(default 0) >>>>>sv_maxrate 8000 // Max bandwidth rate allowed on server, 0 >>>>>== unlimited 8000 == recommend >>>>>sv_minrate 1000 // Min bandwidth rate allowed on server, 0 >>>>>== unlimited 1000 == good 4000 == no dialup >>>>>sv_maxupdaterate 60 // Maximum updates per second that the >>>>>server will allow (default 60) >>>>>sv_minupdaterate 10 // Minimum updates per second that the >>>>>server will allow (default 10) >>>>>sv_maxunlag 1 // Maximum lag compensation in seconds >>>>>(default 1) >>>>>sv_maxvelocity 3500 // Maximum speed any ballistically moving >>>>>object is allowed to attain per axis (default 3500) (Valve Recommends >>>>>3000) >>>>>sv_stats 1 // gather server statistics >>>>>sv_timeout 65 //After this many seconds without a >>>>>message from a client, the client is dropped (default 65) >>>>>sv_unlag 1 //Enables player lag compensation >>>>>sv_voicecodec vaudio_miles //Specifies which voice codec DLL to use >>>>>in a game. Set to the name of the DLL without the extension >>>>> >>>>> >>>>>//----------------------------------------------- >>>>>// Server Ban Variables >>>>>//----------------------------------------------- >>>>>exec banned_user.cfg // execute SteamID based ban list >>>>>exec banned_ip.cfg // execute IP based ban list >>>>>sv_filterban 1 // Set packet filtering by IP mode (default 1) >>>>>sv_logbans 1 // log all bans in logfile >>>>> >>>>>//----------------------------------------------- >>>>>// Server Exec Files >>>>>//----------------------------------------------- >>>>> >>>>>exec mani_server.cfg >>>>> >>>>>//----------------------------------------------- >>>>>// Server Logging Variables >>>>>//----------------------------------------------- >>>>> >>>>>// sv_logsdir "logs/server1" // to separate them from another servers >>>>>logs >>>>>sv_logfile 1 // enable logging and start log file >>>>>(always last thing) >>>>>sv_log_onefile 0 // 1= On 0 = Off >>>>>sv_logecho 1 // 1= On 0 = Off >>>>>log on // 1= On 0 = Off >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>_______________________________________________ >>>>>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
