CoDel AQM discussions
 help / color / mirror / Atom feed
From: "Richard Scheffenegger" <rscheff@gmx.at>
To: "divya singla" <divyasingla1989@gmail.com>,
	<codel@lists.bufferbloat.net>
Subject: Re: [Codel] About Packet Drop in Codel
Date: Thu, 26 Feb 2015 19:32:58 +0100	[thread overview]
Message-ID: <5EDCCC18D27F4F039FA971B3C834A466@srichardlxp2> (raw)
In-Reply-To: <CAONkte9+XLPomhAkwoN6hwGz6a0BkbBDDQF__mGpRaTvB8XcRA@mail.gmail.com>

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

Hi Divya,

is this really the only metric that you are interested in?

What kind of topology and traffic pattern are you using? I would suggest to read the recent posts by Dave Taht around this topic (perhaps looking into ns-3, as the more modern simulator, featuring RRUL test), and also not focus too much on packet loss.


I would think, that the average and induced latency your RED TCP sessions are expiriencing were higher than those governed by CoDel?

What was the effective goodput, and the utilization of  your bottleneck link?

Qualitatively - I'd expect slightly sooner, and sometimes (within an RTT - so not much problem for TCP CC) more losses with Codel (depending where they happen) in order for it to get induced latency under control. But quantitatively, the losses shouldn't be orders of magnitude more, only so much to have a well running control loop there.

Best regards,
  Richard


  ----- Original Message ----- 
  From: divya singla 
  To: codel@lists.bufferbloat.net 
  Sent: Thursday, February 26, 2015 6:12 PM
  Subject: [Codel] About Packet Drop in Codel


  Hi Members,
  i am doing M.tech and my research topic is AQM.
  i tried to run codel with ns-2.35.
  And i found packet loss is more in codel as compared to RED.
  is there anybody who also thinks the same or is it in my case only?
  Am i doing something wrong?




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


  _______________________________________________
  Codel mailing list
  Codel@lists.bufferbloat.net
  https://lists.bufferbloat.net/listinfo/codel

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

  reply	other threads:[~2015-02-26 18:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 17:12 divya singla
2015-02-26 18:32 ` Richard Scheffenegger [this message]
2015-02-26 23:14   ` Stephen Hemminger
2015-03-02 17:43     ` divya singla
2015-03-02 18:10       ` Rick Jones
2015-03-02 18:22       ` Jonathan Morton
2015-03-02 18:43         ` divya singla
2015-03-02 19:07           ` Jonathan Morton
2015-03-03 18:12             ` divya singla
2015-03-03 18:27               ` Rick Jones
2015-03-02 18:35       ` Jonathan Morton
     [not found] <mailman.153549.1425025588.1815.codel@lists.bufferbloat.net>
2015-02-28  1:57 ` David Collier-Brown

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=5EDCCC18D27F4F039FA971B3C834A466@srichardlxp2 \
    --to=rscheff@gmx.at \
    --cc=codel@lists.bufferbloat.net \
    --cc=divyasingla1989@gmail.com \
    /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