Re: [hybi] Encourage disabling Nagle in the standard text?

Andy Green <andy@warmcat.com> Wed, 19 April 2017 02:57 UTC

Return-Path: <andy@warmcat.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE3B812EBD1 for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 19:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NHZSHTRA-eWW for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 19:57:47 -0700 (PDT)
Received: from mail.warmcat.com (mail.warmcat.com [163.172.24.82]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 661E312945A for <hybi@ietf.org>; Tue, 18 Apr 2017 19:57:47 -0700 (PDT)
Date: Wed, 19 Apr 2017 10:57:04 +0800
In-Reply-To: <CAHixhFryAoF=no7_RkzxrkLFOSpSG3ACB1yBUtETp9A00sjsxw@mail.gmail.com>
References: <CAHixhFryAoF=no7_RkzxrkLFOSpSG3ACB1yBUtETp9A00sjsxw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: hybi@ietf.org, Adam Rice <ricea@chromium.org>, "hybi@ietf.org" <hybi@ietf.org>
From: Andy Green <andy@warmcat.com>
Message-ID: <B6D0F181-1482-4331-ADE1-FE92BE743208@warmcat.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/tmlM0PYXoLA69rAJmaOXQi8QTX8>
Subject: Re: [hybi] Encourage disabling Nagle in the standard text?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 02:57:50 -0000


On April 19, 2017 10:34:33 AM GMT+08:00, Adam Rice <ricea@chromium.org> wrote:
>Numerous developers have run into issues when using WebSocket servers
>that
>have the Nagle algorithm enabled [Citation:
>https://www.google.com/search?q=websocket+nagle]. My impression is that
>this ends up with most WebSocket servers disabling Nagle.
>
>I am wondering if it would be better if the standard had text to the
>effect
>that implementations SHOULD disable Nagle (ie. set TCP_NODELAY on the
>socket).
>
>Does anyone have any use cases where Nagle is beneficial?
>
>For reference, Chrome always disables Nagle. pywebsocket doesn't (but
>probably should).

libwebsockets always disables Nagle... AFAIK there is no value to it for general ws use.  But I dunno it needs the standard changing, if things have higher than expected latencies people will probably work it out for themselves.

-Andy