I know that NGinx is very, very fast in handling redirects, but there may have to be some redirects that will affect performance in a meaningful way, if I know how many redirects there will be, I will feel more Good. Hundreds? Tens of thousands? million?
We are able to handle a lot of traffic by caching popular pages in Memcached for a minute or two (reducing the load on our database, which is an obvious bottleneck), but NGinx still has to route that traffic.
< p>Is this something I should care about? How many redirects are there too many high-traffic sites?
[Edit: as suggested, I also posted on ServerFault]
[Edit: this is the answer I accepted on ServerFault]
A redirect is not really a problem as
there’s no backend being contacted.
Just Nginx. And Just Nginx is really,
really fast. As in 10,000+ connections
per second fastYou should probably worry more about a
cluttered configuration file before
you worry about if Nginx can handle
it.
I am working on a news center website that has been around for many years and is steadily increasing page redirects. Currently we have about 375 redirects, and an increase of about 5-10 per month.
I know that NGinx is very, very fast in handling redirects, but there must be some redirects. The way it makes sense affects performance, if I knew how many redirects there would be, I would feel better. Hundreds? Tens of thousands? million?
We are able to handle a lot of traffic by caching popular pages in Memcached for a minute or two (reducing the load on our database, which is an obvious bottleneck), but NGinx still has to route that traffic.
< p>Is this something I should care about? How many redirects are there too many high-traffic sites?
[Edit: as suggested, I also posted on ServerFault]
[Edit: this is the answer I accepted on ServerFault]
A redirect is not really a problem as
there’s no backend being contacted.
Just Nginx. And Just Nginx is really,
really fast. As in 10,000+ connections
per second fastYou should probably worry more about a
cluttered configuration file before
you worry about if Nginx can handle
it.
“Redirect” means HTTP haeder (301 or 302), so it is easier to serve this header than to serve static files for nginx. I have benchmarked it and it can handle every CPU Core 9k requests per second.