From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] keyboard bloat
Date: Sat, 25 Nov 2017 08:20:31 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1711250803560.32099@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw5BNvvVzRL9e=q6=7dunAH2n+w8ZngR2FfoGX6vkJzj9A@mail.gmail.com>
On Fri, 24 Nov 2017, Dave Taht wrote:
> https://danluu.com/keyboard-latency/
This is very interesting.
This guy is doing "button to pixel" delay testing:
https://www.youtube.com/watch?v=4GnKsqDAmgY
At 2:25 he's also talking about the total chain of events that needs to
happen between input and when you see something on the screen.
I wish there was more focus and testing on these kinds of things, then
perhaps we'd also get more focus on bufferbloat in the network.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2017-11-25 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 2:15 Dave Taht
2017-11-25 5:08 ` Yutaka
2017-11-25 7:20 ` Mikael Abrahamsson [this message]
2017-11-25 17:49 ` Nikolay Shopik
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=alpine.DEB.2.20.1711250803560.32099@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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