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 jyasskin
Recipients jyasskin
Date 2008-02-25.02:30:21
SpamBayes Score 0.0233795
Marked as misclassified No
Message-id <1203906623.93.0.917189380676.issue2184@psf.upfronthosting.co.za>
In-reply-to
Content
Thread.start() used sleep(0.000001) to make sure it didn't return before
the new thread had started. At least on my MacBook Pro, that wound up
sleeping for a full 10ms (probably 1 jiffy). By using an Event instead,
we can be absolutely certain that the thread has started, and return
more quickly (217us).

Before:
$  ./python.exe -m timeit -s 'from threading import Thread'  't =
Thread(); t.start(); t.join()'
100 loops, best of 3: 10.3 msec per loop
$  ./python.exe -m timeit -s 'from threading import Thread; t =
Thread()'  't.isAlive()'
1000000 loops, best of 3: 0.47 usec per loop

After:
$  ./python.exe -m timeit -s 'from threading import Thread'  't =
Thread(); t.start(); t.join()'
1000 loops, best of 3: 217 usec per loop
$  ./python.exe -m timeit -s 'from threading import Thread; t =
Thread()'  't.isAlive()'
1000000 loops, best of 3: 0.86 usec per loop

To be fair, the 10ms isn't CPU time, and other threads including the
spawned one get to run during it. There are also some slightly more
complicated ways to get back the .4us in isAlive() if we want.
History
Date User Action Args
2008-02-25 02:30:24jyasskinsetspambayes_score: 0.0233795 -> 0.0233795
recipients: + jyasskin
2008-02-25 02:30:23jyasskinsetspambayes_score: 0.0233795 -> 0.0233795
messageid: <1203906623.93.0.917189380676.issue2184@psf.upfronthosting.co.za>
2008-02-25 02:30:23jyasskinlinkissue2184 messages
2008-02-25 02:30:22jyasskincreate