linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: "Murray J. Root" <murrayr@brain.org>
Cc: linux-kernel@vger.kernel.org, Con Kolivas <kernel@kolivas.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.0-test6 scheduling(?) oddness
Date: Wed, 01 Oct 2003 14:09:43 +1000	[thread overview]
Message-ID: <3F7A5387.4040702@cyberone.com.au> (raw)
In-Reply-To: <3F7A534B.3020401@cyberone.com.au>



Nick Piggin wrote:

>
>
> Murray J. Root wrote:
>
>> P4 2G
>> 1G PC2700 RAM
>> ASUS P4S533
>> Large tasks (like raytrace rendering) take double the amount of time 
>> they used
>> to take, although the system is nicer to the user while they run. In 
>> 2.6.0-test5 had a little trouble with it and Piggin pointed me to a 
>> patch that
>> fixed it and is now in -test6, however the patch didn't slow the 
>> rendering as
>> much as it does in test6. (Con Koliva's patch, I believe it was).
>> For example - rendering an image that took 15 minutes in 2.5.65 takes 
>> 20 minutes in 2.6.0-test5 (with patch) and 30 minutes in 2.6.0-test6 
>> (raw from
>> kernel.org). Same config options (everything I use builtin - no 
>> modules).
>>
>> A new issue (which also doesn't happen in -test5 with the patch):
>> When running cpu intense tasks, new (large) tasks will not start till 
>> the first
>> one finishes.
>> For example, using POV-Ray 3.5 to render an image that takes 30 
>> minutes when it
>> is the only program running, start oowriter.
>> The render finishes in the same 30 minutes, then oowriter starts.
>> oowriter takes about 3 seconds to load if no rendering is going on.
>> I can use apps that are already open but can't start new ones while 
>> rendering.
>> In 2.6.0-test5 (with patch) opening oowriter while rendering takes 
>> about 1 minute.
>> In 2.5.65 opening oowriter while rendering takes about 2 minutes (and 
>> X gets
>> very hard to use till oowriter is completely done opening).
>>
>
> Hi Murray!
> Con Kolivas' patch has been included in test6. You might have tried that
> or maybe my patch?
>
> Anyway, lets just clarify your report:
> 1 CPU, hyperthreading on or off?
>
> test5 interactivity under load isn't as good as test6.
>
> povray takes 150% more time in test6 vs tset5. How many compute threads
> does povray use? Is anything else running? 


Sorry, 150% _the_ time, 50% more time.

>
>
> oowriter takes 3 seconds to load when nothing is running
> oowriter takes 30(or more) minutes to load when povray is runnnig, takes
> 1 minute in test5 plus patch (could you tell us exactly what the patch
> is)
>
>


  reply	other threads:[~2003-10-01  4:09 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 [this message]
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
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=3F7A5387.4040702@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=murrayr@brain.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;
as well as URLs for NNTP newsgroup(s).