All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	"CK Mailinglist" <ck@vds.kolivas.org>
Subject: [ANNOUNCE] DeskOpt - on fly task, i/o scheduler optimization
Date: Fri, 31 Aug 2007 17:35:38 +0200	[thread overview]
Message-ID: <46D8354A.3030208@googlemail.com> (raw)

Hi,

Here is something that might be useful for gamers and audio/video editors
http://www.stardust.webpages.pl/files/tools/deskopt/

You can easily tune CFS/CFQ scheduler params

sched_batch_wakeup_granularity_ns
sched_latency_ns
sched_min_granularity_ns
sched_runtime_limit_ns
sched_stat_granularity_ns
sched_wakeup_granularity_ns

back_seek_max
back_seek_penalty
fifo_expire_async
fifo_expire_sync
quantum
slice_async
slice_async_rq
slice_idle
slice_sync

+ nice levels

Results from Nexuiz benchmark

|-------------------------------------------------------------------------------------------|
|	                                      |    CFS + CFQ 	  |   CFS + CFQ + DeskOpt * |
|-------------------------------------------------------------------------------------------|
| timedemo demos/demo2                        |	41,395896833 fps  |   41,460051233 fps      |
| timedemo demos/demo2 + massive_intr 4 1000  |	18,343223633 fps  |   37,814504933 fps      |
| timedemo demos/demo2 + massive_intr 8 1000  |	9,334974533 fps   |   37,376611267 fps      |
|-------------------------------------------------------------------------------------------|

* default class for games

DeskOpt has many design flaws, but it works for me :)

Regards,
Michal

-- 
LOG
http://www.stardust.webpages.pl/log/

             reply	other threads:[~2007-08-31 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 15:35 Michal Piotrowski [this message]
2007-08-31 17:39 ` [ANNOUNCE] DeskOpt - on fly task, i/o scheduler optimization Arjan van de Ven
2007-08-31 18:07   ` Michal Piotrowski
2007-08-31 22:26 ` Chris Snook
2007-08-31 23:13   ` Michal Piotrowski
2007-09-01 22:10 ` Andi Kleen

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=46D8354A.3030208@googlemail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=ck@vds.kolivas.org \
    --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 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.