Well, let me start off by saying I was wrong. Looking at an old Episode One backtrace I see that it only had two threads. I've fired up an OrangeBox Counter-Strike: Source server. Here are the threads: http://pastebin.com/eJNpYsuK
<http://pastebin.com/Za2UzfcH>Thread 4 is SourceMod, which would not be there on a Vanilla server. Took that with 20 bots ingame, but the result should still be the same. If I were to look in htop I would see one main work thread, with one thread (SourceMod?) doing a bit of work once in a while. Then there would be three idle threads hanging out near the bottom of my process list. But anyways, we are straying from the original question. Kyle. On Sat, Sep 4, 2010 at 5:04 PM, Tomas Turbado <[email protected]> wrote: > Thx kyle, thats what i was trying to say. > Once you start a server it spawns 2 threads, the bash script and the real > server process(sometimes more than 1 thread). Once the main process is > started the os select one core an assign that process the core. The process > keep there using just that core until its killed. When i say oragebox or > gold engine dont support multi core/cpu i mean 1 process cant use more than > 1 cpu/core. It is the os who assign process to cores not the engine itself. > Im wrong? > The problem with running lot of small cpu usage server is unless you have a > pretty good system to set process affinity you may have problems with too > many process in 1 cpu and the other ones free. Thats why i wonder if its > better to have higher cpu clock than cores. > > > > > > _______________________________________________ > 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
