Fwd: [ module ] Add http upstream keep alive timeout parameter

Wei Xu weixu365 at gmail.com
Fri Jan 5 04:53:46 UTC 2018


Is it possible to merge the upstream keep alive feature first? because it's
a valuable and simple patch.

We're using React server render, and by adding Nginx as the reverse proxy
on each server, our AWS EC2 instances count reduced 25%, from 43 to 27-37
C4.Large instances.

I wrote a detailed article to explain what happened and why it works at:

The only problem now is we still using the custom patched version, which
makes it *difficult to share the solution with other teams*. So back to the
initial question, is it possible to merge this feature first, and you can
create separate patches if you need to add more features later.



On Thu, Nov 23, 2017 at 3:00 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
> On Wed, Nov 22, 2017 at 05:31:25PM +1100, Wei Xu wrote:
> > Hi,
> >
> > Is there any place to view the status of current proposed patches? I'm
> not
> > sure if this patch had been accepted, still waiting or rejected?
> >
> > In order to avoid errors in production, I'm running the patched version
> > now. But I think it would be better to run the official one, and also I
> can
> > introduce this solution for 'Connection reset by peer errors' to other
> > teams.
> The patch in question is sitting in my patch queue waiting for
> further work - I consider introducing keepalive_requests at the
> same time, and probably $upstream_connection and
> $upstream_connection_requests variables.
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20180105/5e575681/attachment.html>

More information about the nginx-devel mailing list