All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
To: linux-kernel@vger.kernel.org, vlc-devel@videolan.org
Subject: Low os-jitter operating system.
Date: Sun, 16 Sep 2012 22:34:33 +0200	[thread overview]
Message-ID: <op.wkqwrvza6426ze@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.02.1105201819310.3078@ionos>

Hiya, I sendt this to the ubuntu suggestions box. I am emailing a copy  
here aswell.
---


Mark Shuttleworth has talked about "ultrasmooth" gaming, desktop etc. You  
can have that now already, or atleast quite close. Games will be perfect.  
Webanims and videoes will depend on syncing code or target frame rate.

First of all drop unessecary layers from the kernel. Config it for minimal  
latency. (max preemption, more preemption = less os-jitter = less latency)
Standard config usually is not configged this way, and leads to uneccesary  
chopping/frames dropped. That is not the way you want it.

Use low-jitter applications. For instance - Webkit based browsers have  
lower jitter. Resulting in smoother youtube playback among other things.  
Webanimation in general. So you`d want to use Chromium as the default  
browser.

Intelligent priorities for tasks. If you have background tasks that are  
insensitive to jitter and latency (non audio/video/net), let them have  
lower priority and only one cpu, so they are transparent to the user. Etc.  
Automatic lower priority for a wordprocessor for instance, would also fit  
the profile.

Consider system applications with lowest jitter.

This will also prepare the OS well for Wayland which is opengl based.  
Low-jitter = smoothest opengl experience.

You should also consider promoting a refresh rate of 72, as optimal.  
Research shows that many prefer 72hz refresh rate. I can personally also  
confirm that this is a nice rate, quiet and peaceful, and if one shall  
describe it a "minimal psychovisual noise" setting. More seems to only add  
noise to the screen. Less is flickery. I further tuned this to 72.734hz,  
which you can try and confirm, as a "minimal psychovisual noise" profile.
One should also inform about videos with 30fps, should have 60/90hz  
refresh rate, to avoid video-jitter. Or 25fps, 75hz etc. Similar for other  
formats. An automatically changing screenmode syncing mediaplayer would be  
optimal, with 72.734hz as standard mode, for hzadapting games or other.

Peace Be With You.

PS: If you need a video, to test with low-jitter, I have a low-jitter  
video here: This should play smoothly on a well-configged system @ 60hz  
refresh rate. Unfortunately I doubt the clocks are synced, so there still  
will be small jitter. Should not be much though.

http://paradoxuncreated.com/Blog/wordpress/?page_id=70

  parent reply	other threads:[~2012-09-16 20:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20  8:39 2.6.39: crash w/threadirqs option enabled Justin Piszcz
2011-05-20 12:48 ` Thomas Gleixner
2011-05-20 12:51   ` Justin Piszcz
2011-05-20 13:30     ` Thomas Gleixner
2011-05-20 13:49       ` Justin Piszcz
2011-05-20 15:17         ` Thomas Gleixner
2011-05-20 16:10           ` Justin Piszcz
2011-05-20 16:22             ` Thomas Gleixner
2011-05-21  0:00               ` Uwaysi Bin Kareem
2011-06-10  8:17               ` Justin Piszcz
2011-06-10  8:24                 ` Justin Piszcz
2011-06-10 12:52                 ` Thomas Gleixner
2011-06-10 13:07                   ` Justin Piszcz
2011-06-10 13:10                     ` Thomas Gleixner
2011-06-12 12:04                     ` Justin Piszcz
2012-09-16 20:34               ` Uwaysi Bin Kareem [this message]
2011-05-26 16:30             ` Justin Piszcz

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.wkqwrvza6426ze@localhost.localdomain \
    --to=uwaysi.bin.kareem@paradoxuncreated.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vlc-devel@videolan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.