Flutterby™! : Computer Latency

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Computer Latency

2018-03-05 16:51:16.358198+00 by Dan Lyke 3 comments

Computer latency: 1977-2017:

Almost every computer and mobile device that people buy today is slower than common models of computers from the 70s and 80s. Low-latency gaming desktops and the ipad pro can get into the same range as quick machines from thirty to forty years ago, but most off-the-shelf devices aren’t even close.

[ related topics: Games ]

comments in ascending chronological order (reverse):

#Comment Re: Computer Latency made: 2018-03-05 20:21:00.201023+00 by: brainopener [edit history]

Reminds me of this: Microsoft vscode: CPU usage even when idle (due to cursor rendering):

VS Code uses 13% CPU when focused and idle, draining battery. This is likely due to the blinking cursor rendering. I think CPU usage when focused-and-idle could ideally be near-0%.

#Comment Re: Computer Latency made: 2018-03-06 17:01:51.409203+00 by: brainopener

The follow up is pretty good too: https://danluu.com/keyboard-latency/

#Comment Re: Computer Latency made: 2018-03-07 19:12:08.774998+00 by: Dan Lyke

I've been thinking about this problem a bit in audio. Wireless mic setups are pricey, and of course everyone wants to know if they can use Bluetooth. That, of course, adds a 50ms latency, which is too much for live performance.

But as I've been looking at other applications, so much adds latency that can't work live, things that'd be easy with a DSP end up really wanting analog solutions...

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.