This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Thorben, ggenellina, giampaolo.rodola, pitrou, thorben
Date 2008-09-13.11:31:17
SpamBayes Score 1.3113749e-09
Marked as misclassified No
Message-id <1221305479.23.0.100207430016.issue3766@psf.upfronthosting.co.za>
In-reply-to
Content
> 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 :)
History
Date User Action Args
2008-09-13 11:31:21pitrousetrecipients: + pitrou, ggenellina, giampaolo.rodola, Thorben, thorben
2008-09-13 11:31:19pitrousetmessageid: <1221305479.23.0.100207430016.issue3766@psf.upfronthosting.co.za>
2008-09-13 11:31:18pitroulinkissue3766 messages
2008-09-13 11:31:17pitroucreate