thread. question

Jean-Paul Calderone exarkun at
Mon Feb 9 10:42:16 EST 2009

On Mon, 09 Feb 2009 15:34:02 +0000, Tim Wintle <tim.wintle at> wrote:
>Thanks for both replies,
>On Mon, 2009-02-09 at 15:59 +0100, Christian Heimes wrote:
>> You shouldn't use the thread module directly. It's not meant to be used
>> by a user. Please stick to the threading module. You won't notice a
>> slowdown, trust me :)
>I'm aware that thread is being renamed to _thread in python 3.0, but is
>it being depricated or anything like that?
>This is for an app that has been running for quite a long time and it's
>now time for fairly heavy optimisations as load is increasing (Believe
>me, I wouldn't have been looking at the C otherwise) - so I'll see if I
>do notice any effect with threading.

You may want to look into dropping the use of threads (where possible,
eg for handling TCP connections) if you're trying to optimize the app.
Threads come with a lot of overhead that can be avoided by using non-
blocking operations instead.


More information about the Python-list mailing list