From: Caleb Cushing <xenoterracide@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Steam In Home Streaming on ath9k wifi
Date: Sat, 18 Nov 2017 22:14:44 +0000 [thread overview]
Message-ID: <CAAHKNREZf3rLdYa9JX3b6Fi1VeAgDVV_zkoKTvkO31X2Uunudg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
In home streaming is basically a high bandwidth low latency way of
streaming a game so you can play it on another machine. I'm not sure if
this is the best list to talk about this on, but since it involves wifi,
fq-codel, and cake, this seems like the best place maybe, I did start by
talking about this on the forums, but I think I've basically reached the
end of what documented configuration can do on the current LEDE, and
perhaps what can be done currently period. That said maybe I can offer up
this use case and help things improve in the future.
https://forum.lede-project.org/t/sqm-for-video-streaming-and-steam-in-home-streaming-over-wifi/8494/23
I've actually managed to get game streaming mostly smooth, but there's
still an occasional stutter (latency increase from ~5ms to around 100ms,
then it goes away again) that I haven't figured out. happy to provide more
information if it'll help this use case. note, the additional options
mentioned in the forum on src/desthost seem to actually make things worse.
config queue
option debug_logging '0'
option verbosity '5'
option enabled '1'
option interface 'eth0.2'
option upload '5500'
option linklayer 'ethernet'
option overhead '18'
option qdisc_advanced '0'
option qdisc 'cake'
option script 'layer_cake.qos'
option download '38000'
config queue
option enabled '1'
option interface 'wlan1'
option qdisc_advanced '1'
option squash_dscp '1'
option squash_ingress '1'
option ingress_ecn 'ECN'
option egress_ecn 'NOECN'
option qdisc_really_really_advanced '1'
option itarget '1ms'
option etarget '1ms'
option download '260000'
option upload '260000'
option linklayer 'none'
option debug_logging '1'
option verbosity '10'
option qdisc 'fq_codel'
option script 'simplest.qos'
--
Caleb Cushing
http://xenoterracide.com
[-- Attachment #2: Type: text/html, Size: 3061 bytes --]
next reply other threads:[~2017-11-18 22:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 22:14 Caleb Cushing [this message]
2017-11-19 16:28 ` Toke Høiland-Jørgensen
2017-11-19 21:18 ` Caleb Cushing
2017-11-19 21:27 ` Toke Høiland-Jørgensen
2017-11-19 22:03 ` Caleb Cushing
2017-11-19 22:13 ` Dave Taht
2017-11-21 19:08 Hal Murray
2017-11-22 10:31 ` Neil Davies
2017-11-23 17:48 ` Caleb Cushing
2017-11-24 9:20 ` Hal Murray
2017-11-24 9:34 ` Neil Davies
2017-11-26 7:25 ` Caleb Cushing
2017-11-26 7:29 ` Caleb Cushing
2017-11-26 7:55 ` Jan Ceuleers
2017-11-26 10:05 ` Jonathan Morton
2017-11-26 10:53 ` Jan Ceuleers
2017-11-26 10:55 ` Jonathan Morton
2017-11-26 11:54 ` Steinar H. Gunderson
2017-11-26 13:03 ` Jan Ceuleers
2017-11-26 13:05 ` Jan Ceuleers
2017-11-26 13:13 ` Steinar H. Gunderson
2017-11-26 17:53 ` Dave Taht
2017-11-26 18:43 ` Jan Ceuleers
2017-11-26 23:11 ` Dave Taht
2017-12-04 7:24 ` Caleb Cushing
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=CAAHKNREZf3rLdYa9JX3b6Fi1VeAgDVV_zkoKTvkO31X2Uunudg@mail.gmail.com \
--to=xenoterracide@gmail.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