General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Joe Touch <touch@isi.edu>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Tutorial on latency at Sigcomm 2017
Date: Tue, 13 Jun 2017 11:07:07 -0700	[thread overview]
Message-ID: <a824a199-8be5-0c95-7920-bb47bb124636@isi.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]

Hi, all,

I'll be presenting a tutorial on latency at Sigcomm 2017 in Los Angeles,
and invite you all to consider attending.

Please forward this notice as useful.

(COI Disclaimer: Sigcomm tutorial presenters are unpaid, FWIW)

Joe

----------------------------------

ACM SIGCOMM 2017Tutorial
Understanding Latency - A Root Cost and Mitigation Approach
Joe Touch, USC/ISI
Call For Participation - Los Angeles, CA, Friday August 25, 2017

“Time is fleeting,” it has been said. Time delay, or latency, is the one
metric that drives most others. It defines what it means to be *fast*,
and limits us to what is *fast enough*.

Latency has always been a key part of network performance, but recently
it has been elevated to a primary focus for electronic traders, search
engines, name servers, data centers, and home and network routers.
Increases in network bandwidth, router forwarding speed, and end system
computational resources have helped bring latency to the forefront as a
primary concern. New protocols are emerging to address latency as a
primary issue, including Delay Tolerant Networking (DTN) and bufferbloat
mitigations.

This tutorial presents a comprehensive exploration of the impact of
latency on communication. It explores time as a budget to be spent,
over-spent, rebated, and conserved. We explore the root causes of
latency: generating data, transmitting it, processing it, and the impact
of resource sharing through multiplexing and aggregation, as well as
corresponding ways to mitigate each of these causes. We also explore
ways to mask latency that cannot be reduced and to avoid incurring its
cost in the first place. This tutorial provides examples of real system
design and implementations, as well as exploring several key case
studies to provide practical experience that attendees can immediately
apply to their own systems.

http://conferences.sigcomm.org/sigcomm/2017/tutorial-latency.html

[-- Attachment #2: Type: text/html, Size: 2533 bytes --]

                 reply	other threads:[~2017-06-13 18:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a824a199-8be5-0c95-7920-bb47bb124636@isi.edu \
    --to=touch@isi.edu \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox