> On Wednesday 18 February 2015 00:41:34 rikske@deds.nl wrote:
>> 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?
>>
> [..]
>
> 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 Wednesday 18 February 2015 00:41:34 rikske@deds.nl wrote:
>> 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?
>>
> [..]
>
> 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
>

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

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