Thorben <[EMAIL PROTECTED]> added the comment: 2008/9/11 Antoine Pitrou <[EMAIL PROTECTED]>: > > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > You can use setsockopt() to set the TCP_NODELAY flag and see if that > improves things; sending thousands of 4-bytes packets isn't exactly the > expected utilization of TCP.
You are obviously right, but IIRC, I mentioned that this is simply a dummy testcase... 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. Do you think I could get that value down much further? I don't know much about TCP... > As I said, socket.recv() is just a thin wrapper above the same-named C > library function. Your code expects the kernel's TCP stack to send > things as soon as you ask it to, but TCP is a high-level stream protocol > and implementations usually have sophisticated algorithms in order to > minimize the number of individual packets sent over the wire. 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. > By the way, if you want to build network applications (clients and > servers), I suggest you take a look at the Twisted framework. It will > free you from many low-level issues, although it won't prevent you from > shooting yourself in the foot :-) Thanks, I'll make sure to try it out. > _______________________________________ > 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
