From: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
To: david@lang.hm
Cc: linux-kernel@vger.kernel.org
Subject: Re: Minimal jitter = good desktop.
Date: Sat, 06 Oct 2012 15:19:58 +0200 [thread overview]
Message-ID: <op.wlrdzkqh6426ze@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.02.1210051803180.13407@asgard.lang.hm>
In the context of os-jitter, delay/latency is measured as jitter.
Peace Be With You.
On Sat, 06 Oct 2012 03:06:57 +0200, <david@lang.hm> wrote:
> less jitter != less latency
>
> you could (in theory) eliminate jitter by delaying every keypress
> processed for exactly 1 second by having the code paths that process
> keypresses faster insert delays before implementing the results.
>
> that would result in zero jitter, but horrific latency.
>
> latency is how long it takes to do something, jitter is how much the
> latency varies.
>
> normally, if you optimize for one you make the other worse.
>
> If you optimize for latency, you try to finish everything as soon as you
> can. Since some things take longer than others, jitter increases.
>
> David Lang
>
> On Sat, 6 Oct 2012, Uwaysi Bin Kareem wrote:
>
>> Reducing jitter seems central for many things.
>> First of all keypresses seem faster. (less jitter = less latency).
>> Doom 3 and similar jittersensitive OpenGL applications run smoothly,
>> and better than windows. Doom 3 was also my main app to get running
>> well, and measuring jitter in the signalpath of OpenGL improved the
>> overall computing experience.
>>
>> Even youtube videos who are not synced to refresh, with a refresh of
>> 60, and a videofps of 30, runs quite well.
>> http://paradoxuncreated.com/Blog/wordpress/?p=3221
>>
>> System is responsive, and I have only had one problem, and that is
>> packing seems not to work at the moment.
>>
>> For a fast test in Ubuntu, try
>> http://paradoxuncreated.com/Blog/wordpress/?p=2268
>>
>> Definately a recommended config on the desktop.
>>
>> Peace Be With You.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-10-06 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 0:49 Minimal jitter = good desktop Uwaysi Bin Kareem
2012-10-06 1:06 ` david
2012-10-06 13:19 ` Uwaysi Bin Kareem [this message]
2012-10-06 14:53 ` el_es
2012-10-06 18:02 ` Uwaysi Bin Kareem
2012-10-07 1:15 ` el_es
[not found] ` <op.wlsf0fuc6426ze@localhost.localdomain>
[not found] ` <CAEwFKRBk0X7vAh=Sw-imXeSLN8kBjdfWFXw0Vq2GGygS=0yPrA@mail.gmail.com>
[not found] ` <op.wltgb7mg6426ze@localhost.localdomain>
2012-10-07 20:28 ` Uwaysi Bin Kareem
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.wlrdzkqh6426ze@localhost.localdomain \
--to=uwaysi.bin.kareem@paradoxuncreated.com \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
/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