I can confirm there is a slow leak in the L4D dedicated servers. I have informed the L4D team of the issue. Hopefully someone will be able to find it before the next update.
Just FYI. I am monitoring the servers via Munin. I am using the standard memory graph to show when the servers are going into swap, and it is easy to see the slow increase over time of the committed memory. Once this hits your physical memory limit, you will be forced into swap and perf hits the floor. The only way to get around this, is to restart the srcds process. I do this about once a week using a rolling restart of the srcds around 4am. The leak isn't big, but if you have a lot of forked servers, the change is quite large. I have also had to reduce the number of forks to avoid restarting the servers every night. M. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Peter Lindblom Sent: Monday, April 20, 2009 11:11 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] L4D / SRCDS Linux - Memory leak. To get a good picture of the servers use of memory we have to look at more then "top" as ics say. If I look at "top" on our servers I se 15% mem is used by one instance of srcds, the other 3 is using less then 4%. If I then does a "ps aux" then non of srcds is using more then 3-4% mem. Please check this site about memory problems http://rimuhosting.com/howto/memory.jsp We have many servers running and having no problems with memory. its more problems with updates and plugins. But if you want to restart them once a week- use cron, Good Luck ! Peter ----- Original Message ----- From: "ics" <[email protected]> To: "Half-Life dedicated Linux server mailing list" <[email protected]> Sent: Sunday, April 19, 2009 10:43 PM Subject: Re: [hlds_linux] L4D / SRCDS Linux - Memory leak. > Linux reserves all memory to its use so for example cmd top may show > thata all memory is "used" but when the all memory is really on use (as > shown with cmd free), the server first starts swap to disk and when swap > (that's usually 2x the memory installed) runs out, shit hits the fan. > > Just kill the process to free memory and restart it. Its not that big > deal to do once a week, or sooner, depending the count of the servers / > memory on the machine. > > -ics > > Guillaume Parent kirjoitti: >> What the heck? Of course it's a problem! Nobody wants his box to leak >> memory until a crash inevitably happens! >> >>> Linux dont use memory as Windows does. >>> >>> Its not a problem... >>> >>> Peter >>> >> >> _______________________________________________ >> 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
