nginx latency/performance issues
peter_booth at me.com
Fri Jan 5 02:19:29 UTC 2018
Are you running apache bench on the sam for different host?
If your site is to be static published (which is a great idea)
why are you using SSL anyway?
> On 4 Jan 2018, at 6:12 PM, eFX News Development <dev at efxnews.com> wrote:
> Both apache and nginx are on the same machine, just using different IP aliases so I can connect to both via port 443. After more detective work, I think I've narrowed the problem to the aliasing. The first alias which nginx is on is slower than the second where apache is. When I placed nginx on the same ip, but different port than apache, the speed is much better. There must be some ip address priority as the nginx server is new and has zero traffic on it. This is probably out of scope, but if you have any other thoughts or advice, let me know.
> Thanks again for your help on this.
> ----- Original Message -----
> From: Maxim Dounin <mdounin at mdounin.ru>
> To: nginx at nginx.org
> Subject: Re: nginx latency/performance issues
> Date: 1/4/18 11:52:44 AM
>> Depending on what and how you've measured, the difference between
>> ~128ms and ~142ms might be either non-significant, or explainable by
>> different settings, or have some other explanation. You may want
>> to elaborate a bit more on what and how you are measuring. Also,
>> you may want to measure more details to better understand where
>> the time is spent.
>> In any case, both values are larger than 100ms, and this suggests
>> that you aren't measuring local latency. Likely, most of the
>> latency is network-related, and switching servers won't help much
>> here. In particular, if you are measuring latency on real users
>> within your web application, the difference might be due to no
>> established connection and/or no cached SSL session to a separate
>> static site.
>> Maxim Dounin
>> nginx mailing list
>> nginx at nginx.org
> nginx mailing list
> nginx at nginx.org
More information about the nginx