CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: codel@lists.bufferbloat.net
Subject: [Codel] codel at uber
Date: Sun, 8 Apr 2018 22:04:29 -0700	[thread overview]
Message-ID: <CAA93jw6KX9S+5gsSEmKGA7e+=CWJwxzAP22jqHEDcUbG6HZUuw@mail.gmail.com> (raw)

"A dynamic overload detector offers more flexibility and improves
hardware efficiency, especially in a complex service such as ours.
With QALM, we implemented an overload detector inspired by the CoDel
algorithm. A lightweight request buffer (implemented by goroutine and
channels) is added for each enabled endpoint to monitor the latency
between when requests are received from the caller and processing
begins in the handler. Each queue monitors the minimum latency within
a sliding time window, triggering an overload condition if latency
goes over a configured threshold." - https://eng.uber.com/qalm/

-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

                 reply	other threads:[~2018-04-09  5:04 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/codel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAA93jw6KX9S+5gsSEmKGA7e+=CWJwxzAP22jqHEDcUbG6HZUuw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=codel@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