public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@denise.shiny.it>
To: SodaPop <soda@xirr.com>
Cc: Pavel Machek <pavel@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Oscillations in disk write compaction, poor interactive performance
Date: Wed, 18 Apr 2001 20:40:02 +0200	[thread overview]
Message-ID: <3ADDDF82.DB37117B@denise.shiny.it> (raw)
In-Reply-To: <Pine.LNX.4.30.0104170950350.24360-100000@xirr.com>


> The problem is that at the low point in the cycle, the machine is
> unusable.  It is utterly unresponsive until the writes complete, which can
> take a very long time (in the case of the ppc machine, several minutes!)
> Anything that does disk I/O will block for a long time - having 'ls' take
> two minutes is not a good thing.

Can you chack how much cpu time do dbflush and kswapd get ?

> 2.2 does not exhibit this behaviour.

2.2 is much worse IMO.

Bye.


      reply	other threads:[~2001-04-19 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 21:34 Oscillations in disk write compaction, poor interactive performance SodaPop
2001-04-16 15:29 ` Pavel Machek
2001-04-17 14:55   ` SodaPop
2001-04-18 18:40     ` Giuliano Pochini [this message]

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=3ADDDF82.DB37117B@denise.shiny.it \
    --to=pochini@denise.shiny.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=soda@xirr.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