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 neologix
Recipients David.Edelsohn, neologix, pitrou, python-dev, spurin
Date 2014-09-24.17:53:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1h4xnqWe1JqFy9+i9rP=qaQNmorrobwKnq0FYKYX7v=A@mail.gmail.com>
In-reply-to <1411544624.62.0.271885454519.issue17835@psf.upfronthosting.co.za>
Content
> In this case, the issues are being caused by the following kernel parameters that we have for our default build -
>
> #########################
> ## TIBCO network tuning #
> #########################
> net.core.rmem_default = 33554432
> net.core.wmem_default = 33554432
> net.core.rmem_max = 33554432
> net.core.wmem_max = 33554432
>
> Toggling the support.PIPE_MAX_SIZE to +32MB or temporarily removing these parameters mitigates the issue.  Is there a better way of calculating support.PIPE_MAX_SIZE so it is reflective of the actual OS value?

What does:

>>> import fcntl, os
>>> r, w = os.pipe()
>>> fcntl.fcntl(w, 1032)

return?

Note that the kernel buffer sizes above are, well, *really huge*.
History
Date User Action Args
2014-09-24 17:53:22neologixsetrecipients: + neologix, pitrou, python-dev, David.Edelsohn, spurin
2014-09-24 17:53:22neologixlinkissue17835 messages
2014-09-24 17:53:22neologixcreate