From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "end2end-interest@postel.org" <end2end-interest@postel.org>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat paper
Date: Tue, 8 Jan 2013 07:35:30 +0000 [thread overview]
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA0801AF@ESESSMB205.ericsson.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
Hi
Include Mark's original post (below) as it was scrubbed
I don't have an data of bufferbloat for wireline access and the fiber connection that I have at home shows little evidence of bufferbloat.
Wireless access seems to be a different story though.
After reading the "Tackling Bufferbloat in 3G/4G Mobile Networks" by Jiang et al. I decided to make a few measurements of my own (hope that the attached png is not removed)
The measurement setup was quite simple, a Laptop with Ubuntu 12.04 with a 3G modem attached.
The throughput was computed from the wireshark logs and RTT was measured with ping (towards a webserver hosted by Akamai). The location is Luleå city centre, Sweden (fixed locations) and the measurement was made at lunchtime on Dec 6 2012 .
During the measurement session I did some close to normal websurf, including watching embedded videoclips and youtube. In some cases the effects of bufferbloat was clearly noticeable.
Admit that this is just one sample, a more elaborate study with more samples would be interesting to see.
3G has the interesting feature that packets are very seldom lost in downlink (data going to the terminal). I did not see a single packet loss in this test!. I wont elaborate on the reasons in this email.
I would however believe that LTE is better off in this respect as long as AQM is implemented, mainly because LTE is a packet-switched architecture.
/Ingemar
Marks post.
********
[I tried to post this in a couple places to ensure I hit folks who would
be interested. If you end up with multiple copies of the email, my
apologies. --allman]
I know bufferbloat has been an interest of lots of folks recently. So,
I thought I'd flog a recent paper that presents a little data on the
topic ...
Mark Allman. Comments on Bufferbloat, ACM SIGCOMM Computer
Communication Review, 43(1), January 2013.
http://www.icir.org/mallman/papers/bufferbloat-ccr13.pdf
Its an initial paper. I think more data would be great!
allman
--
http://www.icir.org/mallman/
[-- Attachment #2: Bufferbloat-3G.png --]
[-- Type: image/png, Size: 267208 bytes --]
next reply other threads:[~2013-01-08 7:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 7:35 Ingemar Johansson S [this message]
2013-01-08 10:42 ` [Bloat] [e2e] " Keith Winstein
2013-01-08 12:19 ` Ingemar Johansson S
2013-01-08 12:44 ` Keith Winstein
2013-01-08 13:19 ` Ingemar Johansson S
2013-01-08 15:29 ` dpreed
2013-01-08 16:40 ` Mark Allman
2013-01-09 14:07 ` Michael Richardson
2013-01-10 7:37 ` Keith Winstein
2013-01-10 13:46 ` Michael Richardson
2013-01-08 15:04 ` dpreed
2013-01-18 22:00 ` [Bloat] " Haiqing Jiang
[not found] <87r4lvgss4.fsf@toke.dk>
2013-01-09 3:39 ` [Bloat] Bufferbloat Paper Mark Allman
2013-01-09 5:02 ` David Lang
2013-01-18 1:23 ` grenville armitage
-- strict thread matches above, loose matches on Subject: below --
2013-01-08 19:03 [Bloat] bufferbloat paper Hal Murray
2013-01-08 20:28 ` Jonathan Morton
2013-01-09 0:12 ` David Lang
2013-01-09 1:59 ` Mark Allman
2013-01-09 4:53 ` David Lang
2013-01-09 5:13 ` Jonathan Morton
2013-01-09 5:32 ` Mark Allman
2013-01-07 23:37 [Bloat] Bufferbloat Paper Hagen Paul Pfeifer
2013-01-08 0:33 ` Dave Taht
2013-01-08 0:40 ` David Lang
2013-01-08 2:04 ` Mark Watson
2013-01-08 2:24 ` David Lang
2013-01-09 20:08 ` Michael Richardson
2013-01-08 4:52 ` Mark Watson
2013-01-08 1:54 ` Stephen Hemminger
2013-01-08 2:15 ` Oliver Hohlfeld
2013-01-08 12:44 ` Toke Høiland-Jørgensen
2013-01-08 13:55 ` Mark Allman
2013-01-09 0:03 ` David Lang
2013-01-10 13:01 ` Mark Allman
2013-01-09 20:14 ` Michael Richardson
2013-01-09 20:19 ` Mark Allman
2013-01-09 20:31 ` Michael Richardson
2013-01-10 18:05 ` Mark Allman
2013-01-08 14:04 ` Mark Allman
2013-01-08 17:22 ` Dave Taht
2013-01-09 20:05 ` Michael Richardson
2013-01-09 20:14 ` Mark Allman
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=81564C0D7D4D2A4B9A86C8C7404A13DA0801AF@ESESSMB205.ericsson.se \
--to=ingemar.s.johansson@ericsson.com \
--cc=bloat@lists.bufferbloat.net \
--cc=end2end-interest@postel.org \
/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