Re: [aqm] AQM schemes: Queue length vs. delay based

Preethi Natarajan <preethi.cis@gmail.com> Tue, 12 November 2013 23:56 UTC

Return-Path: <preethi.cis@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D60221E80C4 for <aqm@ietfa.amsl.com>; Tue, 12 Nov 2013 15:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.975
X-Spam-Level:
X-Spam-Status: No, score=-0.975 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, SARE_SUB_OBFU_Q1=0.227]
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 v0zMdgzMrI4k for <aqm@ietfa.amsl.com>; Tue, 12 Nov 2013 15:56:35 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B88C821E8089 for <aqm@ietf.org>; Tue, 12 Nov 2013 15:56:35 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id rd3so2552858pab.33 for <aqm@ietf.org>; Tue, 12 Nov 2013 15:56:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type; bh=7sKX40x+xDnV3jnl8ksy44E28CKcRFhFA59Q3hB5ldo=; b=LC0wQ2M4NYtYaEP//JxgPBlNXoVuZE9+3+4mNVL8yB3z0GC1EzIh55PQNEtMnaDNyx sUSRABZagYhJ+I2MQIoxYEIFq7YzVk/biObh7RSgodTnGDtVduGAk8OpDpfY+4VZ7nq6 iuCCZVR811VTFIXTaS36ISwiZF4K9ShQNH0ifDtBniqnJNQe36ReCu96PGbZp+tz876Z rB8N2VvFY7Xh4KkklzkgBwrHxHgn+UH17nVQVK2U16K6xKfOm/PsGa3mUtGcme8xSQEl 9tBQjl+cPlZn1yiNESGS8Voo+gcK10DUiIlt3HtPlJv8CxwXIbn50v2ejvfrQYozTiIs 9Luw==
X-Received: by 10.66.65.234 with SMTP id a10mr10384633pat.165.1384300595258; Tue, 12 Nov 2013 15:56:35 -0800 (PST)
Received: from [10.33.22.215] (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPSA id wp8sm40116162pbc.26.2013.11.12.15.56.32 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 12 Nov 2013 15:56:34 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Tue, 12 Nov 2013 15:56:30 -0800
From: Preethi Natarajan <preethi.cis@gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>, Naeem Khademi <naeem.khademi@gmail.com>
Message-ID: <CEA7FE2F.4B2C5%prenatar@cisco.com>
Thread-Topic: [aqm] AQM schemes: Queue length vs. delay based
In-Reply-To: <E47DE53D-DEFE-4203-A239-C7615E384E65@ifi.uio.no>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3467116593_4601438"
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] AQM schemes: Queue length vs. delay based
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 23:56:36 -0000


From:  Michael Welzl <michawe@ifi.uio.no>
Date:  Friday, November 8, 2013 5:30 PM
To:  Preethi Natarajan <preethi.cis@gmail.com>
Cc:  Naeem Khademi <naeem.khademi@gmail.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject:  Re: [aqm] AQM schemes: Queue length vs. delay based

> 
> Thanks for the link. My point was just (along with Naeem) that it would be
> useful to compare PIE (or CoDel) against something else except CoDel and RED.
> When I just look at the graphs in the HPSR paper (sorry, didn't get to read it
> yet), again I see only PIE, CoDel, RED.
> 
> We tried ARED and were surprised to see how good it works - which is not to
> say that it is the ideal - but it was surprisingly often better than these
> newer schemes, despite its age of 10+ years... as we all know, there are many
> schemes out there, quite often designed with the goal of removing RED's
> dependence on parameters.

Michael, Naeem:

This is just a follow-up to better understand the ARED results presented at
AQM WG (http://www.ietf.org/proceedings/88/slides/slides-88-iccrg-4.pdf).

Could you please clarify whether the ARED parameters for the tests were set
as specified in the 2001 paper? I.e., when average queueing delay target =
1ms, the min and max thresholds would translate to 0.5ms and 1.5ms, and for
5 ms target the min and max thresh will be 2.5ms and 7.5ms, respectively,
right? Can you confirm?

Assuming ARED logic is intact, ARED drops all packets when average queue
size goes above max_thresh  (max_thresh = 1.5ms or 7.5ms etc.); this would
be semantically similar to a drop tail queue with shallow buffer (can be
confirmed by looking at cumulative packet drops by ARED).

This is probably why the delay values are tight for ARED, and why ARED
translates to poor utilization, especially for the lower target delay
values, as seen in your slides (#8, #11, #13).

Also,  wondering if bursty traffic was considered for evaluations, since
semantics of drop tail with shallow buffering doesn't accommodate bursty
traffic. 

Thanks,
Preethi & Rong