[issue27456] TCP_NODELAY

2016-07-07 Thread Jim Fulton
Jim Fulton added the comment: I missed the point that you can get a transport's socket using get_extra_info. IMO, this provides an adequate escape from the default and qualifies as a "proper way to set it". I still think the default should be to enable TCP_NODELAY. --

[issue27456] TCP_NODELAY

2016-07-05 Thread Yury Selivanov
Yury Selivanov added the comment: PR: https://github.com/python/asyncio/pull/373 -- ___ Python tracker ___

[issue27456] TCP_NODELAY

2016-07-05 Thread Yury Selivanov
Yury Selivanov added the comment: > Is there a similar update that can be made to uvloop? Yes. Once it's committed to asyncio, I'll add it to uvloop immediately. That's one benefit of using uvloop -- it gets updates faster ;) -- ___ Python

[issue27456] TCP_NODELAY

2016-07-05 Thread Jim Fulton
Jim Fulton added the comment: Yury, I'd be fine with you making a PR. :) Is there a similar update that can be made to uvloop? -- ___ Python tracker ___

[issue27456] TCP_NODELAY

2016-07-05 Thread Guido van Rossum
Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue27456] TCP_NODELAY

2016-07-05 Thread Yury Selivanov
Yury Selivanov added the comment: Jim, I can make a PR, unless you want to do that. -- ___ Python tracker ___

[issue27456] TCP_NODELAY

2016-07-05 Thread Jim Fulton
Jim Fulton added the comment: I forgot to switch to the asyncio branch of ZEO when testing on the Amazon/RedHat linux. When I do, the tests run slow there too. Asyncio is dog slow on every linux I've tried. -- ___ Python tracker

[issue27456] TCP_NODELAY

2016-07-05 Thread Guido van Rossum
Guido van Rossum added the comment: Fine with me -- I have no idea what this flag does (nor the desire to learn :-). -- ___ Python tracker ___

[issue27456] TCP_NODELAY

2016-07-05 Thread Yury Selivanov
Yury Selivanov added the comment: See also https://github.com/python/asyncio/issues/286 I also wanted to raise this question. I think transports should set NODELAY by default (as Golang, for instance). I've been hit by this thing a few times already -- performance of protocols over TCP is

[issue27456] TCP_NODELAY

2016-07-05 Thread Jim Fulton
Jim Fulton added the comment: Gaaa, forgot to set meta data. -- components: +asyncio nosy: +gvanrossum, haypo, yselivanov type: -> performance versions: +Python 3.4, Python 3.5 ___ Python tracker

[issue27456] TCP_NODELAY

2016-07-05 Thread Jim Fulton
New submission from Jim Fulton: tl;dr TCP_NODELAY should be set by default and/or there should be a proper way to set it. I've ported ZEO, ZODB's client-server networking layer to asyncio. Things were going pretty well. I've been developing on a Mac. Yesterday, I ran some performance