On Nov 4, 2006, at 5:51 AM, Ian mu wrote:
If people post their specs, settings and then maybe a graph of cpu usage (maybe on different maps and player numbers), then I think it may be easier for either a trend to be seen, or Valve to realise there is actually a problem. As it is, its hard to pluck anything concrete out (apart from people believe there's a problem, but its not enough really no matter how true it is without something more specific provided to them)
Thank you. Personally, nothing is more annoying than going through a thread expecting it to go somewhere, but more-or-less coming to the conclusion that no one is going to do anything about it but whine. If those interested in fixing the problem really want to solve this, provide as much detail as you can: about the hardware, the software (and settings) running on the system, and the environment used to generate the load. Provide comparisons on equivalent hardware and stress. Saying "wah wah it's broken" does nothing good for the situation without this kind of information. In fact, a lesser development team would listen to this and optimize in the wrong spot, making portability (64-bit server anyone?) even harder to achieve. I'm in no position to do this myself, but I'd be more than happy to assist anyone that can generate statistical data on windows/linux, on equivalent hardware that needs a little help getting all the information for a good performance test case. -- Erik Hollensbe [EMAIL PROTECTED] _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
