On Sun, Dec 03, 2017 at 09:49:45AM -0800, cpol...@vt.edu wrote:
> On Tuesday, June 23, 2009 at 11:09:30 PM UTC-4, Aahz wrote:
> > In article ,
> > =?UTF-8?Q?Filip_Gruszczy=C5=84ski?= wrote:
> > >
> > >I have encountered a performance problem using suds, which was traced
> > >down to _socket.recv.
On Sun, Dec 03, 2017 at 09:49:45AM -0800, cpol...@vt.edu wrote:
> On Tuesday, June 23, 2009 at 11:09:30 PM UTC-4, Aahz wrote:
> > In article ,
> > =?UTF-8?Q?Filip_Gruszczy=C5=84ski?= wrote:
> > >
> > >I have encountered a performance problem using suds, which was traced
> > >down to _socket.recv.
On Tuesday, June 23, 2009 at 11:09:30 PM UTC-4, Aahz wrote:
> In article ,
> =?UTF-8?Q?Filip_Gruszczy=C5=84ski?= wrote:
> >
> >I have encountered a performance problem using suds, which was traced
> >down to _socket.recv. I am calling some web services and each of them
> >uses about 0.2 sec and 9
In article ,
=?UTF-8?Q?Filip_Gruszczy=C5=84ski?= wrote:
>
>I have encountered a performance problem using suds, which was traced
>down to _socket.recv. I am calling some web services and each of them
>uses about 0.2 sec and 99% of this time is spent on urllib2.urlopen,
>while the rest of the call
