From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
To: Dave Taht <dave.taht@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Cc: martino.trevisan@dia.units.it, francois.michel@uclouvain.be,
danilo.giordano@polito.it
Subject: Re: [Starlink] paper: a first look at starlink performance
Date: Fri, 28 Oct 2022 11:21:06 +0200 [thread overview]
Message-ID: <ef9efc8a-91d1-fe4c-faf9-94ff49dfd956@uclouvain.be> (raw)
In-Reply-To: <CAA93jw4BUHiunARt-7YPUo3Hv8ecJ-7TMo3+F0TG7dTdNxx6MQ@mail.gmail.com>
Dave,
> So nice to see olivier's name pop up on this (yay!) open access publication:
>
> https://dl.acm.org/doi/pdf/10.1145/3517745.3561416
>
> I would have liked if they had tracked the starlink bandwidth
> distributions over time as I did here:
> https://docs.google.com/document/d/1puRjUVxJ6cCv-rgQ_zn-jWZU9ae0jZbFATLf4PQKblM/edit
>
> and I wonder if the tools they used for their tests are available
> somewhere(?), so they can be repeated over time, especially as more
> ISL links go up.
All the data is available, including pcaps for all experiments
https://smartdata.polito.it/a-first-look-at-starlink-performance-open-data/
François can give you more details about the QUIC implementations used
for the measurements if you'd like to reproduce them in your testbed.
The main benefit of QUIC compared to TCP is that it provides more data
about packet losses and allowed us to explore packet loss bursts
Olivier
prev parent reply other threads:[~2022-10-28 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 16:23 Dave Taht
2022-10-26 8:21 ` Nitinder Mohan
2022-10-28 9:21 ` Olivier Bonaventure [this message]
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef9efc8a-91d1-fe4c-faf9-94ff49dfd956@uclouvain.be \
--to=olivier.bonaventure@uclouvain.be \
--cc=danilo.giordano@polito.it \
--cc=dave.taht@gmail.com \
--cc=francois.michel@uclouvain.be \
--cc=martino.trevisan@dia.units.it \
--cc=starlink@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