Re: FOUNDIT (was Re: massive threading performance)

2006-04-25 Thread Paul Sijben
Lawrence D'Oliveiro wrote: > In article <[EMAIL PROTECTED]>, > Paul Sijben <[EMAIL PROTECTED]> 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.setblo

Re: FOUNDIT (was Re: massive threading performance)

2006-04-22 Thread Lawrence D'Oliveiro
In article <[EMAIL PROTECTED]>, Paul Sijben <[EMAIL PROTECTED]> 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 relevan

FOUNDIT (was Re: massive threading performance)

2006-04-20 Thread Paul Sijben
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