public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Meder <chris@onestepahead.de>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6 vs 2.4 regression when running gnomemeeting
Date: Sat, 20 Dec 2003 02:52:59 +0100	[thread overview]
Message-ID: <1071885178.1044.227.camel@localhost> (raw)
In-Reply-To: <3FE3A53F.6090203@cyberone.com.au>

[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]

On Sat, 2003-12-20 at 02:26, Nick Piggin wrote:
> Christian Meder wrote:
> 
> >On Sat, 2003-12-20 at 01:48, Nick Piggin wrote:
> >
> >>Sounds reasonable. Maybe its large interrupt or scheduling latency
> >>caused somewhere else. Does disk activity alone cause a problem?
> >>find / -type f | xargs cat > /dev/null
> >>how about
> >>dd if=/dev/zero of=./deleteme bs=1M count=256
> >>
> >
> >Ok. I've attached the logs from a run with a call with only an
> >additional dd. The quality was almost undisturbed only very slightly
> >worse than the unloaded case.
> >
> 
> OK, its probably not that then. Try the find command though, it would
> be closer to what make/gcc is doing.

Ok. I've attached the find load log. Doesn't feel different from the dd
disk load case. Quality is almost undisturbed.

> 
> >
> >>You said it faired slightly better with my scheduler when renicing
> >>gnome meeting to -10. How much better is that?
> >>
> >
> >Worse than unloaded and worse than the disk loaded case from above. But
> >all (CPU) loaded cases were producing almost complete audio dropouts
> >while with your scheduler and renicing to -10 I got at least a
> >stuttering audio stream (a regular pattern of very short slices of audio
> >mixed with very short slices of silence).
> >
> 
> So it does sound like scheduling latency then. Its difficult to find
> out what is happening with top and vmstat because they don't give you
> an idea of individual scheduling events, which is what is important
> for things like this. I'll have a look into making up a patch to gather
> what I want to know.

Ok. I will try it then.

> 
> In the meantime, I have a newer scheduler patch against 2.6.0 you could
> try: http://www.kerneltrap.org/~npiggin/v28p1.gz

Is this patch supposed to be different schedulerwise from the scheduler
rollup patches against 2.6.0-testx

> Try nicing the compile to +19 if it still stutters.

Ok. I'll try it but I'm not too optimistic about the outcome ;-)


			Christian Meder

-- 
Christian Meder, email: chris@onestepahead.de
 
What's the railroad to me ?
I never go to see
Where it ends.
It fills a few hollows,
And makes banks for the swallows, 
It sets the sand a-blowing,
And the blackberries a-growing.
                      (Henry David Thoreau)
 




[-- Attachment #2: findload.tar.bz2 --]
[-- Type: application/x-bzip, Size: 8963 bytes --]

  reply	other threads:[~2003-12-20  1:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 20:11 2.6 vs 2.4 regression when running gnomemeeting Christian Meder
2003-12-19 20:32 ` William Lee Irwin III
2003-12-19 23:30   ` Christian Meder
2003-12-20  0:21     ` Nick Piggin
2003-12-20  0:37       ` Christian Meder
2003-12-20  0:48         ` Nick Piggin
2003-12-20  1:11           ` Christian Meder
2003-12-20  1:26             ` Nick Piggin
2003-12-20  1:52               ` Christian Meder [this message]
2003-12-20  2:38                 ` Nick Piggin
2003-12-20  2:55                   ` Con Kolivas
2003-12-20  3:32                     ` Christian Meder
2003-12-20  3:50                       ` Nick Piggin
2003-12-20  4:16                         ` Christian Meder
2003-12-20  4:32                           ` Nick Piggin
2003-12-20  5:15                             ` Christian Meder
2003-12-20  8:31                               ` Con Kolivas
2003-12-20 11:19                               ` Ingo Molnar
2003-12-20 16:17                                 ` Christian Meder
2003-12-20 16:49                                 ` Christian Meder
2003-12-20 17:42                                   ` Ingo Molnar
2003-12-21  1:40                                     ` Christian Meder
2003-12-21  8:57                                       ` Ingo Molnar
2003-12-22  1:19                                         ` Christian Meder
2003-12-22  1:47                                           ` Con Kolivas
2003-12-22  8:48                                           ` Ingo Molnar
2003-12-20 23:29                                   ` Nick Piggin
2003-12-20 22:20                         ` Matthias Andree
2003-12-21 19:23                           ` Jens Axboe
2003-12-22 10:54                       ` Andrew McGregor
2003-12-22 11:15                         ` Con Kolivas
2003-12-22 12:51                         ` Ingo Molnar
2003-12-22 13:25                         ` Nick Piggin
2003-12-20 19:34 ` Marc Schiffbauer
2003-12-21  1:49   ` Christian Meder

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=1071885178.1044.227.camel@localhost \
    --to=chris@onestepahead.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    --cc=wli@holomorphy.com \
    /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