General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Alex Burr <ajb44.geo@yahoo.com>
To: bloat <bloat@lists.bufferbloat.NET>
Subject: Re: [Bloat] Skype
Date: Sun, 18 Nov 2012 08:09:03 -0800 (PST)	[thread overview]
Message-ID: <1353254943.93761.YahooMailNeo@web126202.mail.ne1.yahoo.com> (raw)
In-Reply-To: <647D57F5-24CE-4006-AD2A-74141C84C3CB@ifi.uio.no>

I have noticed delays - although I don't think multiple seconds - but I think that it may be skype trying to make the best of a bad connection. I don't have any knowledge of the internals of the skype client, but I suspect that they take the view that delayed audio is better than incomprehensible audio - I think I have even heard it actually repeating the last bit of audio before a glitch, to give you a better chance to understand the next bit, and presumably catching up when the opportunity arises. 

So, an experiment to rule out skype might need to use not just a de-bloated path, but one with known packet loss.


Alex



----- Original Message -----
> From: Michael Welzl <michawe@ifi.uio.no>
> To: bloat <bloat@lists.bufferbloat.NET>
> Cc: 
> Sent: Sunday, November 18, 2012 2:57 PM
> Subject: [Bloat] Skype
> 
> Hi,
> 
> I have repeatedly noticed that Skype sometimes, in a long conversation involving 
> video, can create massive audio delays (in the order of multiple seconds). This 
> has happened to me in a conversation from a hotel room in the US to my home in 
> Oslo (where, apologies, I haven't yet looked into de-bloating my modem and 
> access point), and from my office in Oslo to someone else's office in the 
> US.
> 
> I'm wondering: was that always due to bloated equipment along the path 
> (including the end hosts), or does Skype poorly handle its internal buffers?
> 
> Any experiences? I suppose the way to find out is to run Skype over a verifiably 
> de-bloated path. If, then, the problem never occurs, the fault is with the 
> equipment and not with Skype (and vice versa).
> 
> Cheers,
> Michael
> 
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
> 

  reply	other threads:[~2012-11-18 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 14:57 Michael Welzl
2012-11-18 16:09 ` Alex Burr [this message]
2012-11-19 10:27 Ingemar Johansson S
2012-11-19 10:36 ` Dave Taht
2012-11-19 13:25 ` Michael Welzl
2012-11-19 18:23   ` Matt Mathis

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=1353254943.93761.YahooMailNeo@web126202.mail.ne1.yahoo.com \
    --to=ajb44.geo@yahoo.com \
    --cc=bloat@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