public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mohammad R Nikseresht <nikser@ccsl.carleton.ca>
To: linux-kernel@vger.kernel.org
Subject: lowering interactive scheduling latency with no TTYs
Date: Wed, 08 Dec 2010 09:42:05 -0500	[thread overview]
Message-ID: <4CFF993D.3050504@ccsl.carleton.ca> (raw)

Hi,

I have developed a Linux scheduling enhancement that gives significantly
lower scheduling latency for interactive processes (20+% improvement
versus the Mike Galbraith's recent "200 line" scheduling patch, 80+%
improvement versus 2.6.35 stock scheduler) but without any reference to
TTYs or use of cgroups.  It also reduces latency for network server
processes under background load (mysql, apache).

My enhancement is currently implemented as a SystemTap script; as a
result general scheduling latency is currently a bit high.  I am
currently working on translating it into a kernel patch.

More information is here, including a full description in a technical
report, benchmarks, and my SystemTap script:

   http://people.scs.carleton.ca/~mniksere/appeasement.html

What follows is a brief description of how Customer Appeasement
scheduling works.

The basic idea behind my enhancement, which I call the Customer
Appeasement scheduling policy, is to boost the priority of critical processes
based upon their socket-level interactions. The assumption is that the processes that are 
interacting with a customer have a higher non-zero socket read operations.
Based on this I increase their priority temporary whenever they have a non-zero socket 
read operation to let them to respond to the customer request faster.
The exact amount of priority increase and the time interval that the process 
receives this extra priority depends on the system load. The higher the system load
the higer the priority and the longer the time interval.

Please try running it, I'd appreciate your feedback,

Thanks,

--
Mohammad Nikseresht



                 reply	other threads:[~2010-12-08 15:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CFF993D.3050504@ccsl.carleton.ca \
    --to=nikser@ccsl.carleton.ca \
    --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