From: Helge Hafting <helgehaf@aitel.hist.no>
To: Ed Tomlinson <tomlins@cam.org>, linux-kernel@vger.kernel.org
Subject: Re: o(1) to the rescue
Date: Fri, 18 Jan 2002 11:21:10 +0100 [thread overview]
Message-ID: <3C47F716.A192DB3F@aitel.hist.no> (raw)
In-Reply-To: <20020118030630.AA34757D57@oscar.casa.dyndns.org>
Ed Tomlinson wrote:
>
> Try this with and without the o(1) scheduler (J0).
>
> Create a dir full of 1 meg or so jpegs. Fire up kde. Try using the
> Tools/Create image gallery.
> With the standard scheduler linux is unusable - it stalls for most of the
> processing time for
> each image. With o(1) its just a little jerky - still usable though (a
> gallery is building as I
> type this).
I guess this thing starts a thread per image? That would
give a lot of _running_ processes, which is exactly what
the O(1) scheduler improves.
Helge Hafting
next prev parent reply other threads:[~2002-01-18 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 3:06 o(1) to the rescue Ed Tomlinson
2002-01-18 10:06 ` Nero
2002-01-18 10:21 ` Helge Hafting [this message]
2002-01-18 12:31 ` Ed Tomlinson
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=3C47F716.A192DB3F@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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.