Re: nginx.conf File too Large

Server NGINX
1

Alexandr,

As of right now we are only using the configuration for one of our
customers
in beta and nginx is not giving any errors. Before we migrate more
customers onto the platform we wanted to get a better idea of the
hypothetical ramifications of having such a large config file. What are
the
best practices for config files and what could go wrong if we have a
large
number of hosts configured onto one nginx server each with a lot of
conditions?

Thanks,
Rami

Date: Wed, 6 Jul 2011 22:41:49 +0300
From: Alexandr G. [email protected]
To: [email protected]
Subject: Re: nginx.conf File too Large
Message-ID:
[email protected]
Content-Type: text/plain; charset=ISO-8859-1

On 7/6/11, Rami E. [email protected] wrote:

We are trying to use nginx as a reverse proxy for a large number of sites
and putting up a lot of rules to direct and traffic for each host. Is
there
a number of hosts ({server}) that would be too many for a single nginx
instance to support? At what point does the configuration file get too
large
and start bogging down the nginx server? Currently each host takes up
about
150 lines, and we are looking to put in 25+ hosts onto each server. I
wanted
to know if this realistic?

It doesn’t sound like an nginx problem. Nginx usually suggests what to
change if it hits the limit. Can you show us the exact error message?

2

It just depends what you consider a large configuration. For example we
have a bunch of Ngnix instances running each with roughly 200,000 lines
of configuration, although taking just the raw number of lines as such
might be a bad metric.

Posted at Nginx Forum:

3

Thanks for the advise. I guess the only way is to try it and keep an
eye on
the performance.