From: Andrew Morton <akpm@digeo.com>
To: alan@cotse.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] 2.5.46-mm1 with contest
Date: Thu, 07 Nov 2002 16:48:03 -0800 [thread overview]
Message-ID: <3DCB09C3.1EDB05EC@digeo.com> (raw)
In-Reply-To: YWxhbg==.5c396bf3e8e65dc7442a4adb6f35702e@1036715544.cotse.net
Alan Willis wrote:
>
> > Why? We are preempting during the generic file write/read routines, I
> > bet, which can otherwise be long periods of latency. CPU is up and I
> > bet the throughput is down, but his test is getting the attention it
> > wants.
>
> I'm curious, would running contest after a fresh boot and with profile=2
> provide a profile that tells exactly where time is being spent? Since
> about 2.5.45 I've had some strange slow periods, and starting aterm
> would take a while, redrawing windows in X would slow down, it 'feels'
> like my workstation becomes a laptop that is just waking up. Sometimes
> this is after only a few minutes of inactivity, or after switching
> virtual desktops in kde, or when I have alot of aterm instances running.
- Run `vmstat 1', and see if the slowdowns coincide with any unusual
IO activity.
- Could be the scheduler. Try
renice -19 $(pidof X) $(pidof aterm) $(pidof other stuff)
next prev parent reply other threads:[~2002-11-08 0:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 0:32 [BENCHMARK] 2.5.46-mm1 with contest Alan Willis
2002-11-08 0:48 ` Andrew Morton [this message]
2002-11-08 21:08 ` Alan Willis
2002-11-08 21:21 ` Andrew Morton
[not found] ` <YWxhbg==.a11f3fbc6d68c50c7f190513c1d3bacf@1037045821.cotse.net>
2002-11-11 21:03 ` Andrew Morton
2002-11-11 21:11 ` Alan Willis
2002-11-11 21:32 ` Andrew Morton
2002-11-13 0:14 ` Denis Vlasenko
2002-11-12 20:07 ` Alan Willis
-- strict thread matches above, loose matches on Subject: below --
2002-11-07 22:53 Con Kolivas
2002-11-07 23:48 ` Robert Love
2002-11-07 23:58 ` Andrew Morton
2002-11-08 0:04 ` Robert Love
2002-11-08 6:04 ` Con Kolivas
2002-11-08 0:10 ` Benjamin LaHaise
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=3DCB09C3.1EDB05EC@digeo.com \
--to=akpm@digeo.com \
--cc=alan@cotse.com \
--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 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.