200ms Delay With SPDY - Nginx 1.6.x?

Dear,

While searching for Nginx optimize patches:

https://josephscott.org/archives/2014/12/nginx-1-7-8-fixes-200ms-delay-with-spdy/

Came to my attention.

Can anyone confirm if the ‘200ms Delay With SPDY’ problem also applies
to
Nginx 1.6.x?

Thanks,

Regards,

Rik Ske

On Wednesday 18 February 2015 00:41:34 [email protected] wrote:

[…]

It applies to all versions up to 1.7.8.

Also note, that it’s always a good idea (and strongly recommended) to
stick
to the latest version especially if you’re using new or/and experimental
modules like SPDY.

The “stable” branch receives only critical bugfixes, and misses many
other.

See also: http://nginx.com/blog/nginx-1-6-1-7-released/

wbr, Valentin V. Bartenev

On 2/18/15 5:42 PM, [email protected] wrote:

You can’t optimize a site to the max without SPDY.

That’s doesn’t match our experience.

Also, enabling SPDY doesn’t make your site faster automagically. It
is not a silver bullet.


Maxim K.
http://nginx.com

http://nginx.com


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

Hi Maxim,

That is the same as the website is not working after installing Nginx.
Every situation requires configuration.

Greetings,

Rik SKe

to

It applies to all versions up to 1.7.8.

wbr, Valentin V. Bartenev

Hi Valentin,

Thank you very much for the comment. I’d appreciate it a lot.

From server production perspective, The ‘mainline’ branch is not really
useful. Not only the SPDY code changed but everything changed or can
change. This gives a lot of extra time to test everything through and
through.

So it is strongly recommended to use stable code as far as possible in
any
production environment.

And about experimental modules like SPDY. Yes you are right its
experimental. But for web servers you have no choice now days.
You can’t optimize a site to the max without SPDY.

Coming back to 200ms.
200ms extra, unnecessary delay is deadly for a web server.

All the way in a world dominated by internet search engines where every
ms
counts.

It’s like a heart attack.
I do not understand that this problem is not referred as critical bug.
It
should even be a blocker.

Your changelog writes about: ‘now the “tcp_nodelay” directive works with
SPDY connections’. This is a major loss of function because the existing
1.6. tcp_nodelay won’t work as it should be.

Can you re-evaluate a patch for 1.6.?

Thanks,

Greetings,

Rik Ske

Maxim K.
That is the same as the website is not working after installing Nginx.


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

Hi Maxim,

Understood. Apart from the fact what SPDY can mean for someone specific.
There is a flaw in and which prevents “tcp_nodelay” in Nginx 1.6. to
function correctly.

How to fix that.

Gr

Rik Ske

[…]

Hi Maxim,

Understood. Apart from the fact what SPDY can mean for someone specific.
There is a flaw in and which prevents “tcp_nodelay” in Nginx 1.6. to
function correctly.

How to fix that.

There are several options:

  • you can backport 1.7 diff to 1.6;

  • you can use 1.7 in production (this is what we actually recommend
    to do; e.g. nginx-plus based on 1.7 branch currently).

We will discuss merging this code to 1.6 for the next release but we
don’t have a schedule for 1.6.3 yet.


Maxim K.
http://nginx.com

http://nginx.com


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

Hi Maxim,

Thanks, your help is mutch appriciated.
Regards,

Rik Ske

On 2/18/15 6:57 PM, [email protected] wrote:

http://nginx.com
Every situation requires configuration.

I’ve just tried to point out that assertion “you can’t optimize a
site to the max without SPDY” is not always true.

Btw, one of the case I am talking about is the site in the alexa top100.


Maxim K.
http://nginx.com

Hi,

On 2/18/15 7:35 PM, [email protected] wrote:

  • you can backport 1.7 diff to 1.6;

  • you can use 1.7 in production (this is what we actually recommend
    to do; e.g. nginx-plus based on 1.7 branch currently).

We will discuss merging this code to 1.6 for the next release but we
don’t have a schedule for 1.6.3 yet.
[…]

Hi Maxim,

Thanks, your help is mutch appriciated.
Regards,

This bugfix was merged to 1.6 and will be a part of 1.6.3 release
which is out today.


Maxim K.
http://nginx.com

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs