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 mkc
Recipients akuchling, giampaolo.rodola, intgr, josiahcarlson, klimkin, mkc
Date 2009-03-31.20:12:27
SpamBayes Score 0.00058550667
Marked as misclassified No
Message-id <1238530349.2.0.353234217425.issue2073@psf.upfronthosting.co.za>
In-reply-to
Content
Just to confirm, the real problem here was that tiny packets were being
sent out by default, and the obvious fix (altering ac_out_buffer_size)
didn't work.

Looking at the code, it appears that the change by Josiah Carlson
(#64062) causes ac_out_buffer_size (which currently defaults to 4096) to
be obeyed.

Should that 4096 be larger?  MTU for jumbo packets is ~9000, I think,
plus there's less system call overhead for larger values.  (I use 62000
for my app, but I haven't studied alternatives lately.)

Also, there are still two constants '512' in asyncore/asynchat. 
Shouldn't these be changed to match the 4096 default?
History
Date User Action Args
2009-03-31 20:12:29mkcsetrecipients: + mkc, akuchling, josiahcarlson, klimkin, giampaolo.rodola, intgr
2009-03-31 20:12:29mkcsetmessageid: <1238530349.2.0.353234217425.issue2073@psf.upfronthosting.co.za>
2009-03-31 20:12:28mkclinkissue2073 messages
2009-03-31 20:12:27mkccreate