FOUNDIT (was Re: massive threading performance)

Paul Sijben sijben at eemvalley.com
Tue Apr 25 11:31:47 EDT 2006


Lawrence D'Oliveiro wrote:
> In article <44476e82$0$31650$e4fe514c at news.xs4all.nl>,
>  Paul Sijben <sijben at eemvalley.com> wrote:
> 
>> I found that the problem was caused by the sending thread not giving
>> control back quickly enough to the receiving thread.
>>
>> Also in going through the code I found an old self.s.setblocking(0)call
>> that was no longer relevant. Removing that solved my problem.
>>
>> Something that took 20 seconds now takes just 1.
> 
> You might also find that it goes still faster if you forego threading 
> and use a select.select loop.

thanks for that. I will have to try it.



More information about the Python-list mailing list