Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Ignore:
Timestamp:
May 19, 2011, 3:18:44 AM (14 years ago)
Author:
rgrieder
Message:

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 #.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • code/trunk/src/libraries/core/Core.cc

    r8423 r8505  
    8686
    8787#ifdef ORXONOX_PLATFORM_WINDOWS
    88     SetCommandLineArgument(limitToCPU, 1).information("Limits the program to one CPU/core (1, 2, 3, etc.). Default is the first core (faster than off)");
     88    SetCommandLineArgument(limitToCPU, 0).information("Limits the program to one CPU/core (1, 2, 3, etc.). Default is off = 0.");
    8989#endif
    9090
Note: See TracChangeset for help on using the changeset viewer.