From: "Murray J. Root" <murrayr@brain.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test6 scheduling(?) oddness
Date: Wed, 1 Oct 2003 01:10:08 -0400 [thread overview]
Message-ID: <20031001051008.GD1416@Master> (raw)
In-Reply-To: <20030930215512.1df59be3.akpm@osdl.org>
On Tue, Sep 30, 2003 at 09:55:12PM -0700, Andrew Morton wrote:
> "Murray J. Root" <murrayr@brain.org> wrote:
> >
> > The render finishes in the same 30 minutes, then oowriter starts.
> > oowriter takes about 3 seconds to load if no rendering is going on.
>
> OpenOffice uses sched_yield() in strange ways which causes it to
> get hopelessly starved on 2.6 kernels. I think RH have a fixed version,
> but I don't know if that has propagated into the upstream yet.
>
> So... Don't worry about OpenOffice too much. Is the problem reproducible
> with other applications?
Nope - even tried it with KDE apps.
Write it off to OpenOffice, not test6.
That doesn't explain the major time increase of the render, though.
200% for 2.5.65 vs 2.6.0-test6 or 150% for 2.6.0-test5 vs 2.6.0-test6 is a
bit extreme.
--
Murray J. Root
next prev parent reply other threads:[~2003-10-01 5:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 3:22 2.6.0-test6 scheduling(?) oddness Murray J. Root
2003-10-01 4:08 ` Nick Piggin
2003-10-01 4:09 ` Nick Piggin
2003-10-01 4:35 ` Murray J. Root
2003-10-01 4:55 ` Andrew Morton
2003-10-01 5:04 ` Nick Piggin
2003-10-01 5:18 ` Murray J. Root
2003-10-01 6:53 ` Andrew Morton
2003-10-01 7:19 ` Murray J. Root
2003-10-01 5:10 ` Murray J. Root [this message]
2003-10-01 21:47 ` bill davidsen
2003-10-01 22:30 ` Ed Sweetman
2003-10-06 2:29 ` bill davidsen
2003-10-06 17:02 ` Murray J. Root
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=20031001051008.GD1416@Master \
--to=murrayr@brain.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox