From: Mike Galbraith <efault@gmx.de>
To: Mike Mestnik <cheako@mikemestnik.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Chronic resource starvation.
Date: Mon, 16 Jan 2012 03:39:34 +0100 [thread overview]
Message-ID: <1326681574.6446.25.camel@marge.simson.net> (raw)
In-Reply-To: <4F1322A6.7090009@mikemestnik.net>
On Sun, 2012-01-15 at 13:01 -0600, Mike Mestnik wrote:
> On 01/15/12 06:08, Mike Galbraith wrote:
> >> Does this behavior look normal or is it just my system? If it is normal
> >> how difficult would it be to make corrections and would those
> >> corrections likely be kernel or application related?
> > That "Backup complete" makes me suspect a classic case of IO-itis. If
> > bits of your GUI were pushed out or ram (or weren't previously used),
> > and live on a disk you're beating hell out of, you get to experience
> > horrid interactivity while those missing bits are being retrieved.
> Thank you for the reply!
>
> That's DVDShrink, copies from optical drive(slow) to disk(fast-ish?).
> http://www.dvdshrink.info/
>
> That wouldn't explain why the monitor(gkrellm) stopped updating, every
> part of that is pooling like top would. Gkrellm indicates disk activity
> and it shows the backup complete on sr1 and a backup in progress on sr0,
> however neither of these operations rate on Disk or sda.
No, dvdshrink wouldn't do enough IO to matter much. Heavy IO can (or
could) cause symptoms like your video though, all of it. I used to be
able to trigger loss of GUI control for 30 minutes at a time. All it
took was something poking fdatasync after a large streaming IO had been
running for a while.
Another IO thing that can cause horrible interactivity is IO error
recovery. That can (or again, could) make a box lurch like hell. If
that were the cause, you'd have kernel gripes in dmesg output.
-Mike
next prev parent reply other threads:[~2012-01-16 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 3:17 Chronic resource starvation Mike Mestnik
2012-01-14 20:21 ` Mike Mestnik
2012-01-15 12:08 ` Mike Galbraith
2012-01-15 19:01 ` Mike Mestnik
2012-01-16 2:39 ` Mike Galbraith [this message]
2012-01-16 5:43 ` Mike Mestnik
2012-01-16 5:51 ` Mike Galbraith
2012-01-16 6:07 ` Mike Galbraith
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=1326681574.6446.25.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=cheako@mikemestnik.net \
--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