Re: H2 Server Push performance data

Tom Bergan <tombergan@chromium.org> Mon, 22 July 2019 18:06 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D93BC1200E3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Jul 2019 11:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.751
X-Spam-Level:
X-Spam-Status: No, score=-2.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=chromium.org
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 4IJKHx_Zd3ya for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Jul 2019 11:06:22 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49531120089 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 22 Jul 2019 11:06:22 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hpcez-0008Rl-TE for ietf-http-wg-dist@listhub.w3.org; Mon, 22 Jul 2019 18:03:41 +0000
Resent-Date: Mon, 22 Jul 2019 18:03:41 +0000
Resent-Message-Id: <E1hpcez-0008Rl-TE@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <tombergan@chromium.org>) id 1hpcex-0008Qz-B4 for ietf-http-wg@listhub.w3.org; Mon, 22 Jul 2019 18:03:39 +0000
Received: from mail-yb1-xb2c.google.com ([2607:f8b0:4864:20::b2c]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <tombergan@chromium.org>) id 1hpceP-00042h-Su for ietf-http-wg@w3.org; Mon, 22 Jul 2019 18:03:31 +0000
Received: by mail-yb1-xb2c.google.com with SMTP id x188so10645847yba.8 for <ietf-http-wg@w3.org>; Mon, 22 Jul 2019 11:02:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qHX3JtfSC5AW19PLekxmIeg4O79XN3VtIDKOXIMqO5A=; b=bCRmNakplFDgGs90p3B6z7BJNW02+Ehtk906dAtM6JqcADiVs/Ud+JTH4RkqGQPAco 8yT33pfcrNGctWOuS3H3hb37T1fuye9OzIgHz8TW5OqMYFQI4YNPA/m12qT4bCBidKT1 bXGAuzfsvUc1UVGqiZD+PyiopXyHPi/N1GvAU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qHX3JtfSC5AW19PLekxmIeg4O79XN3VtIDKOXIMqO5A=; b=AOFGhqSzcV8onlHRQ51/YZmZL9Fm10VEnVIXf4hKpWHJf4zBo94WZ7DYToFUwaep8/ eqH5LWmrTc61OjYo3lqllPw+KCudfCXizrMZFeNvm04+Bp2LlfhVIRSuxtqweJslffqd Hs2uvkwhfWsfqImxYjrVEGpRTAPda4HO/Wu0MpGGDOvCbzvbznwdWJHkcW/l3yMKXAJ6 gzM5Wzw84YW+jdANrd+8kPaZX4WSmCzMkxuWX008xizQkMzMqKVsq/Wubk9qQeoRMip7 pvVhTpOd3J/Vcw4H7wPLEYB9SABjTj/gxu6sih59WDcDyLgWs9nx5utoXFboCTh0sc5S J5ig==
X-Gm-Message-State: APjAAAVslTBRPvd/b8OxTBRfiLtUdS2HszdOhhCIeuDZNMwbKNQSJRV7 jM1spenLGL5VQ9foBsYeHane40tLmFU=
X-Google-Smtp-Source: APXvYqwwskBNgFH8isTk/GnwFyb0qN0Tkdgf2GsfG8O5cq1z1YUAzqU7k/dXAzTHavRMgbJoqes7ew==
X-Received: by 2002:a25:d10a:: with SMTP id i10mr46551926ybg.101.1563818562846; Mon, 22 Jul 2019 11:02:42 -0700 (PDT)
Received: from mail-yw1-f41.google.com (mail-yw1-f41.google.com. [209.85.161.41]) by smtp.gmail.com with ESMTPSA id z6sm9845869ywg.40.2019.07.22.11.02.42 for <ietf-http-wg@w3.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jul 2019 11:02:42 -0700 (PDT)
Received: by mail-yw1-f41.google.com with SMTP id x74so16116373ywx.6 for <ietf-http-wg@w3.org>; Mon, 22 Jul 2019 11:02:42 -0700 (PDT)
X-Received: by 2002:a0d:ea06:: with SMTP id t6mr38991166ywe.186.1563818561753; Mon, 22 Jul 2019 11:02:41 -0700 (PDT)
MIME-Version: 1.0
References: <8EA56456-0299-4D60-B97A-E6FCD27D9231@akamai.com>
In-Reply-To: <8EA56456-0299-4D60-B97A-E6FCD27D9231@akamai.com>
From: Tom Bergan <tombergan@chromium.org>
Date: Mon, 22 Jul 2019 11:02:29 -0700
X-Gmail-Original-Message-ID: <CA+3+x5H9eF5mNGbLU_M3ZN=Jfe4PdstoeeZ-56G1UOZfRdOO4w@mail.gmail.com>
Message-ID: <CA+3+x5H9eF5mNGbLU_M3ZN=Jfe4PdstoeeZ-56G1UOZfRdOO4w@mail.gmail.com>
To: "Nanner, Aman" <ananner@akamai.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000de571d058e48e124"
Received-SPF: pass client-ip=2607:f8b0:4864:20::b2c; envelope-from=tombergan@chromium.org; helo=mail-yb1-xb2c.google.com
X-W3C-Hub-Spam-Status: No, score=-3.9
X-W3C-Hub-Spam-Report: AWL=0.201, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1hpceP-00042h-Su b1855ded493ce055deb830a6868ea078
X-Original-To: ietf-http-wg@w3.org
Subject: Re: H2 Server Push performance data
Archived-At: <https://www.w3.org/mid/CA+3+x5H9eF5mNGbLU_M3ZN=Jfe4PdstoeeZ-56G1UOZfRdOO4w@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36816
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hi Aman,

Interesting results, thanks for sharing! I do wonder why you decided to
compare means instead of percentiles? It looks like there are some crazy
bad outliers. Assuming your "April 2019 Results with Old Methodology" and
"April 2019 Results (1% quantile excluded)" graphs use the same set of
sites in the same order, the mean goes from about +500ms to -200ms. If 99%
of requests on that site take -200ms, the last 1% must take 70s! Instead of
means, you could have compared medians, or 25th/75th percentiles, or other
percentiles in the distribution. You can compute confidence intervals on
percentiles. You can also do something like Mann-Whitney to check if the
distributions differ significantly.

I'd also like to hear more about this linear regression that you run on the
A/B results. I couldn't follow why this regression is necessary. If your
A/B test uses i.i.d. coin flips, you can compute confidence intervals
directly on the A/B results. Is your A/B test not i.i.d.? How do you know
the linear regression doesn't introduce bias?

Also, have you looked into measuring other metrics, such as
FirstContentfulPaint?

-Tom

On Mon, Jul 22, 2019 at 4:41 AM Nanner, Aman <ananner@akamai.com> wrote:

> At the previous IETF 102 HTTPWG session in Montreal, I had presented some
> Akamai data on H2 Server Push which can be found here:
>
>
> https://github.com/httpwg/wg-materials/blob/gh-pages/ietf102/akamai-server-push.pdf
>
> Akamai has conducted some more recent tests with a tweaked methodology
> (exclusion of 1% highest-latency requests on the long-tail), and we have
> found some interesting results. I share some more details about the
> performance analysis here:
>
>
> https://medium.com/@ananner/http-2-server-push-performance-a-further-akamai-case-study-7a17573a3317
>
> Thanks,
> Aman Nanner
> Akamai Technologies Inc.
>
>