The CPU usage that SRCDS manages to chug is borderline
suicidal for the end result, not to mention the countless places in
the engine where memory continues to leak like a sieve

I agree with this, in general, but I don't think 'syscalls' is the issue here. You need to exclude everything but the main thread to get rid of the numerous helper/packet threads that spend their time waiting for a signal or polling a socket. The 'gettimeofday' is more an example of lack of effort at profiling/optimizing srcds than it is a majority of CPU usage.

The only real issue, then, I see with this profile is the fsync() calls. Something tells me those are occuring on the main thread. That's bad.

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to