Upstream performances: what if one node only ?

Nicolas Flinois nicolas.flinois at amadeus.com
Fri Jun 27 16:39:20 UTC 2014


Many thanks Maxim.

Have a nice week-end..

Nicolas FLINOIS 
ALTEN Contracting Company 
Amadeus, Sales & e-Commerce Platform 
T: + 33 (0) 4 92 94 63 50 (Ext:6350) 
nicolas.flinois at amadeus.com 
www.amadeus.com/



From:   Maxim Dounin <mdounin at mdounin.ru>
To:     nginx at nginx.org, 
Date:   27/06/2014 18:35
Subject:        Re: Upstream performances: what if one node only ?
Sent by:        nginx-bounces at nginx.org



Hello!

On Fri, Jun 27, 2014 at 03:53:24PM +0200, Nicolas Flinois wrote:

> Hi all,
> 
> I am wondering about the possible extra-cost of using a single-node 
> upstream into proxy_pass compared with  'proxy_pass host' directly.
> I need to automate application servers move, and find convenient to 
update 
> upstream definitions only (defined into dedicated files).
> 
> Solution1:
> 
> upstream upOne {
>     server somehost;
> }
> [..]
> proxy_pass upOne;
> 
> 
> Solution2:
> 
> proxy_pass somehost;
> 
> Is solution1 more time-consuming than solution2 at run-time ?

There is no difference.  Internally, proxy_pass with a hostname 
creates an implicit upstream{} with a single server, and uses it.

-- 
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140627/f1c65349/attachment.html>


More information about the nginx mailing list