On Fri, Mar 3, 2017 at 8:57 PM, Tony Mobily <m...@mobily1.com> wrote: > > > >> That's my case, the proxy we use is a custom built node http proxy based >> solution that does not use keep-alive on the backend requests. >> > > That's interesting. How come you built your own? >
We needed business logic to implement the routing of the incoming requests to different backend service providers. It turned out to be very simple to implement the logic atop of node-http-proxy. > I assumed that a keepalive connection from the client to the nginx server > would imply a keep-alive connection from nginx to the local node server > listening to an unprivileged port... but that's obviously not the case! > (Does that even matter? Would you ever want a keep-alive connection > between the proxy and the local node?) > It would make sense to use a keep-alive strategy to the backend whenever the cost of establishing the connections outweighs the price (memory footprint, usually) of maintaining idle open connections for the keep-alive period. In cases where the proxy and the upstream have very little latency between them I'd wager that there's very little, if any, performance advantage in using keep-alive. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAD%2BcU%2B7%3Dw3RvxaUs14fUTs4hQB%3D4dhWudo0OEEJJW-voTKAiug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
