mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jake Moilanen <moilanen@austin.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Williams <pwil3058@bigpond.net.au>
Subject: [ANNOUNCE 0/4] Genetic-lib version 0.2
Date: Tue, 15 Feb 2005 13:29:06 -0600	[thread overview]
Message-ID: <20050215132906.33f88505.moilanen@austin.ibm.com> (raw)

Here is the next release of the genetic library based against 2.6.10
kernel.

There were numerous changes from the first release, but the major change
in this version is the introduction of phenotypes.  A phenotype is a set
of genes the affect an observable property.  In genetic-library terms,
it is a set of genes that will affect a particular fitness measurement. 
Each phenotype will have a set of children that contain genes that
affect a fitness measure.  

Now multiple fitness routines can be ran for each genetic library user.
Then depending on the results of a particular fitness measure, the
specific genes that directly affect that fitness measure can be
modified.  This introduces a finer granularity that was missing in the
first release of the genetic-library.  

I would like to thank Peter Williams for reworking the Zaphod Scheduler
and help designing the phenotypes.

Some of the other features introduced is shifting the number of
mutations depending on how well a phenotype is performing.  If the
current generation outperformed the previous generation, then the rate
of mutation will go down.  Conversely if the current generation performed
worst then the previous generation, the mutation rate will go up.  This
mutation rate shift will do two things.  When generations are improving,
it will reduce the number unnecessary mutations and hone in on the
optimal tunables.  When a workload drastically changes, the fitness
should go way down, and the mutation rate will increase in order to test
a greater space of better values quicker.  This should decrease the time
it takes to adjust to a new workload.  There is a limit at 45% of the
genes being mutated every generation in order to prevent the mutation
rate spiralling out of control. 

SpecJBB and UnixBench are still yielding a 1-3% performance improvement,
however (though it's subjective) the interactiveness has had noticeable
improvements.

I have not broke the Anticipatory IO Scheduler down to a fine
granularity in phenotypes yet.  Any assistance would be greatly
appreciated.

Currently I am hosting this project off of:

	http://kernel.jakem.net

[1/4 genetic-lib]: This is the base patch for the genetic algorithm.

[2/4 genetic-io-sched]: The base patch for the IO schedulers to use the
       genetic library.

[3/4 genetic-as-sched]: A genetic-lib hooked anticipatory IO scheduler.

[4/4 genetic-zaphod-cpu-sched]: A hooked zaphod CPU scheduler.  Depends
       on the zaphod-v6.2 patch.

Thanks,
Jake


             reply	other threads:[~2005-02-15 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 19:29 Jake Moilanen [this message]
2005-02-15 19:34 ` [ANNOUNCE 1/4] " Jake Moilanen
2005-02-15 19:37 ` [ANNOUNCE 2/4] " Jake Moilanen
2005-02-15 19:39 ` [ANNOUNCE 3/4] " Jake Moilanen
2005-02-15 19:56 ` [ANNOUNCE 4/4] " Jake Moilanen

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=20050215132906.33f88505.moilanen@austin.ibm.com \
    --to=moilanen@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwil3058@bigpond.net.au \
    /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

all inboxes | Powered by JetHome®