Re: [hybi] frame length encoding

Pieter Hintjens <ph@imatix.com> Sat, 21 August 2010 20:27 UTC

Return-Path: <pieterh@gmail.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10E6E3A67B2 for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 13:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.966
X-Spam-Level:
X-Spam-Status: No, score=-1.966 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNbL24V2d8+z for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 13:27:34 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id A37DF3A659C for <hybi@ietf.org>; Sat, 21 Aug 2010 13:27:34 -0700 (PDT)
Received: by vws10 with SMTP id 10so4497499vws.31 for <hybi@ietf.org>; Sat, 21 Aug 2010 13:28:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=gCx479jwDwaFF5xumSchWSi2aPP0BSkNrS3Yhw9g5M0=; b=FIHpouNXTdxWZea0rABW+vbhjC7W6fC1Pa7MkbwHlZ72saXJJwb0IgmcCKS5J2hoVW 0eaqYKR0SRS6Eq1OWRlgeM77lj7rDd9fBlGbM79FzCKr/7kSysdI+San/xmSnpx/82EK vb5cbaTbyq/5PvBtEFGsGnofl+DgLVjkmCr7I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=mx45iTgyuPy5eQDhuvjm8GQXHshpXKPpY605lmoik3ZcaKBDS7/HCNshIf5x1dIBWW v1kQqVceHuA655wRt8seCg7OSQOTtbVNs33wmJbfTeS2mqDOzNHx/oXcKwo7nPAozwET /avCVrZe5Bt1Lr2tsQDUD64M8+sxNd/Ak8kGw=
Received: by 10.220.60.204 with SMTP id q12mr1980276vch.45.1282422488221; Sat, 21 Aug 2010 13:28:08 -0700 (PDT)
MIME-Version: 1.0
Sender: pieterh@gmail.com
Received: by 10.220.167.17 with HTTP; Sat, 21 Aug 2010 13:27:48 -0700 (PDT)
In-Reply-To: <AANLkTin2sNji3J98VqacammHFS=DJHmpq5zY_mTFNt8Z@mail.gmail.com>
References: <AANLkTimKbmcpgx8k0uXUWvCO=8w9pPrtV=3y4qh6363k@mail.gmail.com> <20100820192927.GA32620@1wt.eu> <4C6EEA55.2050205@hs-weingarten.de> <AANLkTinHqxUOZaVANFpC52t8FfgNw2L5_A-s9Az3Fm7p@mail.gmail.com> <AANLkTinvkxMP8FYz9xjDu_Kt9FfzYotgsqXUDB4MZMEo@mail.gmail.com> <AANLkTim3KRq1arso7wN_b+1TH3sWabYW6uFu7AbYw6-P@mail.gmail.com> <AANLkTikhhajho895WyEoJMwMk9GJ98kA0Mjy5qr4apC8@mail.gmail.com> <AANLkTi=kdk6BRvza_7bpoLNTFzUkjcRRijGLMe_NGXZV@mail.gmail.com> <AANLkTi=VE298Tg+qyfufhzMswE5pBxtPZhA0t2k=sf2A@mail.gmail.com> <AANLkTin2sNji3J98VqacammHFS=DJHmpq5zY_mTFNt8Z@mail.gmail.com>
From: Pieter Hintjens <ph@imatix.com>
Date: Sat, 21 Aug 2010 22:27:48 +0200
X-Google-Sender-Auth: bipq-3Ffl_MLDNXERAKpCAaWkx8
Message-ID: <AANLkTinRgLYg=-hhgtUD__=PqM82Y0nB6HPGkMca3-pw@mail.gmail.com>
To: John Tamplin <jat@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] frame length encoding
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 21 Aug 2010 20:27:36 -0000

On Sat, Aug 21, 2010 at 10:11 PM, John Tamplin <jat@google.com> wrote:

> Obviously, I don't know the details of your environment, but I suspect CPU
> speed will continue to increase faster than network speeds.

CPU core count increases but I think it's fair to say CPU speeds have
hit the top of the curve.  Thus we're constrained by the capacity of
one core to process the data off a network, while network capacity
continues to double every 18-24 months.

> I am a bit confused at your position -- in one sentence you suggest we
> should add another byte just in case we might use it, yet you are still
> worried about a single AND instruction?  Surely the cost of sending that
> byte is higher than one instruction?

The single AND instruction is not a problem.  Treating messages above
126 bytes as "long" means we miss the sweet spot.

> Regardless of the differences between #0 and #1, it already seemed clear
> that #1 was losing out to #2 or yet more complicated schemes, so I don't
> think option #0, which removes the one advantage compared to #3 or Shelby's
> proposal of preserving a reserved bit, will get any more backers than #1
> did.

Indeed, there are probably very few people in the open source world
concerned with efficiency at the level we are.  I've explained our
experience, and will leave it at that.

Thanks again for steering this issue, consensus is more important here
than the actual design, whatever that may be.

-
Pieter Hintjens
iMatix - www.imatix.com