IETF Logo Mail Archive

Re: [hybi] Call for interest: multiplexing dedicated for WebSocket

Bruce Atherton <bruce@callenish.com> Wed, 22 May 2013 19:31 UTC

Return-Path: <bruce@callenish.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 1AAF111E8151 for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 12:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oRWJhB0lrVnq for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 12:31:37 -0700 (PDT)
Received: from biz82.inmotionhosting.com (biz82.inmotionhosting.com [66.117.4.147]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB4811E8152 for <hybi@ietf.org>; Wed, 22 May 2013 12:31:36 -0700 (PDT)
Received: from [96.50.69.82] (port=50564 helo=[192.168.145.118]) by biz82.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <bruce@callenish.com>) id 1UfEl3-0000xb-OB; Wed, 22 May 2013 12:31:34 -0700
Message-ID: <519D1D0E.5000905@callenish.com>
Date: Wed, 22 May 2013 12:31:26 -0700
From: Bruce Atherton <bruce@callenish.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Zhong Yu <zhong.j.yu@gmail.com>
References: <CAH9hSJZxr+aG7GZa4f-dUOTGj4bnJ+3XxivUX4jei5CMyqN4LQ@mail.gmail.com> <CAH9hSJZUG1f+3Uk=t2=A5i4O9=wPvAisspM=pgmGEH9emTL9-Q@mail.gmail.com> <CAH9hSJZai_UuxW4O6mZcEJT2DJoURtLo16XNci1qkYVWv4HVdg@mail.gmail.com> <007501ce56f0$67f74080$37e5c180$@noemax.com> <519CD6A1.7080708@ericsson.com> <519CE075.4000106@tavendo.de> <CAM5k6X9WmO80hiQZ6_GqK66PAd3of=2ZRi9=VrWj52apA1+=5g@mail.gmail.com> <519D02E7.6040009@tavendo.de> <CAM5k6X8Z-JxrgTy3NAc-wC7zK_AfsWAhqzNKaEY_yZzmz=pZcQ@mail.gmail.com> <CACuKZqHYmF+-zECFrGsHqt0i91jHAzk9Az72=tva_kn=ra2pKA@mail.gmail.com>
In-Reply-To: <CACuKZqHYmF+-zECFrGsHqt0i91jHAzk9Az72=tva_kn=ra2pKA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010507050402080309080607"
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz82.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - callenish.com
X-Get-Message-Sender-Via: biz82.inmotionhosting.com: authenticated_id: bruce+callenish.com/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Call for interest: multiplexing dedicated for WebSocket
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 22 May 2013 19:31:43 -0000

On 22/05/2013 12:00 PM, Zhong Yu wrote:
>
> On Wed, May 22, 2013 at 1:32 PM, John A. Tamplin <jat@jaet.org 
> <mailto:jat@jaet.org>> wrote:
>
>     Servers don't handle tons of long-lived connections very well
>
>
> Is that still true today? Recent server implementations all boast they 
> can handle tons of connections.
>

Tons of short, HTTP Request/Response type connections. John is talking 
about long-lived WebSockets connections, the kind that might hang around 
for days, weeks, even months. It is a different problem.

Think of it this way. Say your server can handle 10K simultaneous 
connections to serve web pages and it takes about 330ms to serve them. 
If every one of those opens a websocket connection, you'll need 30K 
WebSocket connections just to handle a single second of traffic. If on 
average the page is kept open for only an hour, that is 108M connections.

v2.23.0 | Report a Bug | By Email