diff options
| author | Chris Jones <cmsj@tenshu.net> | 2013-04-16 17:37:22 -0700 |
|---|---|---|
| committer | Chris Jones <cmsj@tenshu.net> | 2013-04-16 17:37:22 -0700 |
| commit | 56d8757252b22931c1f3821bff04bd0b0c80d746 (patch) | |
| tree | aaf1df4c7711dbf1a8a4640d706d9c1e30056cc4 | |
| parent | 2bab3fd528f458725fd690fb5abc5b010f1df858 (diff) | |
| download | testrepository-56d8757252b22931c1f3821bff04bd0b0c80d746.tar.gz | |
Document the change of CPU core detection
| -rw-r--r-- | doc/MANUAL.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/MANUAL.txt b/doc/MANUAL.txt index 16bbe80..cb76c66 100644 --- a/doc/MANUAL.txt +++ b/doc/MANUAL.txt @@ -165,10 +165,10 @@ Python module to store the duration of each test. On some platforms (to date only OSX) there is no bulk-update API and performance may be impacted if you have many (10's of thousands) of tests. -On Linux, testrepository will inspect /proc/cpuinfo to determine how many CPUs -are present in the machine, and run one worker per CPU. On other operating -systems, or if you need to control the number of workers that are used, the ---concurrency option will let you do so:: +To determine how many CPUs are present in the machine, testrepository will +use the multiprocessing Python module (present since 2.6). On operating systems +where this is not implemented, or if you need to control the number of workers +that are used, the --concurrency option will let you do so:: $ testr run --parallel --concurrency=2 |