[Orxonox-commit 3829] r8505 - code/trunk/src/libraries/core

rgrieder at orxonox.net rgrieder at orxonox.net
Thu May 19 03:18:45 CEST 2011


Author: rgrieder
Date: 2011-05-19 03:18:44 +0200 (Thu, 19 May 2011)
New Revision: 8505

Modified:
   code/trunk/src/libraries/core/Core.cc
Log:
Do not limit the main thread to the first Core/CPU on Windows. It might slow down the game by a percent or two because Ogre forces the program to reside in the first core when it queries the time, hence potentially rescheduling the application.
On the other hand, limiting the application's main thread to one core has drawbacks when starting Orxonox multiple times without taking care of it by specifying --limitToCPU #.

Modified: code/trunk/src/libraries/core/Core.cc
===================================================================
--- code/trunk/src/libraries/core/Core.cc	2011-05-18 13:19:47 UTC (rev 8504)
+++ code/trunk/src/libraries/core/Core.cc	2011-05-19 01:18:44 UTC (rev 8505)
@@ -85,7 +85,7 @@
 #endif
 
 #ifdef ORXONOX_PLATFORM_WINDOWS
-    SetCommandLineArgument(limitToCPU, 1).information("Limits the program to one CPU/core (1, 2, 3, etc.). Default is the first core (faster than off)");
+    SetCommandLineArgument(limitToCPU, 0).information("Limits the program to one CPU/core (1, 2, 3, etc.). Default is off = 0.");
 #endif
 
     Core::Core(const std::string& cmdLine)




More information about the Orxonox-commit mailing list