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 josiahcarlson
Recipients akuchling, giampaolo.rodola, intgr, josiahcarlson, klimkin, mkc
Date 2009-03-31.21:56:52
SpamBayes Score 5.94179e-08
Marked as misclassified No
Message-id <1238536614.6.0.9019646039.issue2073@psf.upfronthosting.co.za>
In-reply-to
Content
The spare 512 values are for code that I expect no one is actually 
using.

In terms of increasing the buffer size from 4096 to something larger, 
that can be done, but I think that more than just a 10mbit switched lan 
test should be performed.  I would tend to believe that a larger size 
would tend to perform better, but my concern is sending blocks too large 
to the OS and having it say "sorry, but you need to chop it up more" via 
sock.send() returning 1 or 2 (I've experienced this on Windows with 
stdio and sockets).

Considering how easy it is to adjust, and considering that the value is 
respected everywhere that matters (performance-conscious users aren't 
using simple_producer, nor are they using dispatcher_with_send), I think 
that 4096 is sufficient for the time being.  Adjusting it up to 16k in 
Python 2.8/3.2 seems reasonable to me.  Someone ping me in a year ;) .
History
Date User Action Args
2009-03-31 21:56:54josiahcarlsonsetrecipients: + josiahcarlson, akuchling, mkc, klimkin, giampaolo.rodola, intgr
2009-03-31 21:56:54josiahcarlsonsetmessageid: <1238536614.6.0.9019646039.issue2073@psf.upfronthosting.co.za>
2009-03-31 21:56:53josiahcarlsonlinkissue2073 messages
2009-03-31 21:56:52josiahcarlsoncreate