[issue3766] socket.socket.recv broken (unbearably slow)
Antoine Pitrou
report at bugs.python.org
Sat Sep 13 13:31:19 CEST 2008
Antoine Pitrou <pitrou at free.fr> added the comment:
> Yes, obviously. Although adding it to the client socket did make no
> difference after I had already done so for the server. Still
> communication is too slow by orders of magnitude. (Sorry for pointing
> this out again)
Well, if this precise use case is really important for you, I suggest
using Wireshark (or any other packet analyzer) to see what happens in
terms of latency between packets over the wire.
Something else: try replacing "localhost" with "127.0.0.1", perhaps your
DNS resolution eats a lot of time.
> I would greatly appreciate any help on the subject. How do *BSD
> sockets differ from Linux sockets and what do I do to make things
> faster.
I don't know, but I suspect the difference is more in the TCP stack
implementation than in the sockets layer.
In any case, I'm gonna close this bug, as this is very likely not a
Python problem. Please ask further questions on comp.lang.python, lots
of people there may help you :)
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3766>
_______________________________________
More information about the Python-bugs-list
mailing list