All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Jan Knutar <jknutar@nic.fi>
Cc: jamagallon@ono.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Finding what is stuck...
Date: Tue, 02 Sep 2008 10:34:46 +0100	[thread overview]
Message-ID: <48BD08B6.4040707@tuffmail.co.uk> (raw)

Jan Knutar wrote:

> On Tuesday 02 September 2008, J.A. Magallón wrote:
>
>> I'm running 2.6.27-rc5-git2 on an Aspire One.
>> The system is in general pretty responsive, but sometimes it just
>> gets totally stuck. Even the mouse stops.
>>
>> It looks related to disk (SSD) access, but I'm not totally sure.
>
> Are you hitting swap at all? Does it have swap?
>
> On my N810 tablet there can be a huge slowdown if it starts swapping.
> The first time it dips into swap is relatively painless when stuff gets
> written out sequentially, but after that when writes are mostly random
> the throughput drops to a few kilobytes per second, causing massive
> slowdown... The MMC/SD cards hate random write, and I expect SSDs are
> no better.
>
> iostat -x -k 10
> in a terminal is useful. Check the iowait and util% numbers after/during
> slowdown...

My experience on the EeePC is similar.  I didn't look into it much but I
think it helped a lot switching to the "noop" ioscheduler

(echo noop > /sys/block/sda/queue/scheduler)

as opposed to the default CFQ, if you haven't already done so.

Alan

             reply	other threads:[~2008-09-02  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02  9:34 Alan Jenkins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-02  0:04 Finding what is stuck J.A. Magallón
2008-09-02  0:08 ` Arjan van de Ven
2008-09-02  0:12   ` J.A. Magallón
2008-09-03 23:00   ` J.A. Magallón
2008-09-03 23:50     ` Arjan van de Ven
2008-09-02  1:53 ` Jan Knutar

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=48BD08B6.4040707@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=jamagallon@ono.com \
    --cc=jknutar@nic.fi \
    --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.