Thorben <[EMAIL PROTECTED]> added the comment: 2008/9/11 Antoine Pitrou <[EMAIL PROTECTED]>: > > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > >> now thats interesting: >> adding the line "sock.setsockopt(SOL_TCP, TCP_NODELAY, 1) " decreased >> the delay by half. It still is extremely high but it's a start. > > Did you do it on both the client and server sockets?
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) >> Would be interesting to examine the differences between the Perl >> wrapper and the Python wrapper to figure out why Perl "does the right >> thing" in this case and Python doesn't. > > Perhaps the Perl wrapper is less thin as the Python one. In any case, > it's by design if the Python socket wrapper doesn't try to be "smart": > the intent is to provide an access to the C API and let people do what > they want with it. Smart things are relegated to higher-level modules or > libraries. 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 think this might be where the real issue is. Low level networking voodoo. Do you think twisted might help me there? > _______________________________________ > Python tracker <[EMAIL PROTECTED]> > <http://bugs.python.org/issue3766> > _______________________________________ > _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3766> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
