This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients louielu, terry.reedy, vstinner
Date 2017-05-06.02:24:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I have a 6 core, 12 cpu Pentium.  I previously stopped with -j10.  Reading the above, I tried -j14 and -j18.  Times for one run on a quiet system of 'test -jnn -ugui' with a fresh download and debug build were 3:55 (-j10), 3:48, and 3:53.  Not much affect.

A more promising source of reduced running time on this system is shown by the last 4 finish times: 2:42 tarfile (:42), 3:13 zipfile (:43), 3:16 venv (:54), and 3:48 multiprocessing_spawn (2:29).  If m._s. were split into files taking at most  40 seconds, I suspect the total running time would be perhaps 20 seconds less due to better CPU utilization. Currently, the total running time could be from about 30 seconds less to about 2 minutes more depending on when m._s. starts in a randomized run.
Date User Action Args
2017-05-06 02:24:14terry.reedysetrecipients: + terry.reedy, vstinner, louielu
2017-05-06 02:24:14terry.reedysetmessageid: <>
2017-05-06 02:24:14terry.reedylinkissue30263 messages
2017-05-06 02:24:13terry.reedycreate