mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Idrigal \(Eric Rautenkranz\)" <darklordoflinux@hotmail.com>
To: "Paul Boley" <pboley@home.com>, <linux-kernel@vger.kernel.org>
Subject: Re: severe slowdown with 2.4 series w/heavy disk access
Date: Tue, 25 Dec 2001 23:51:15 -0600	[thread overview]
Message-ID: <OE31AHYoHyYGNTrzLHw0000763c@hotmail.com> (raw)
In-Reply-To: <3C295D5C.50EE365D@home.com>

It is quite possible your MB routes all disk access straight through the
processor, while using system ram to cache itself.  Tar does not (to my
knowledge) limit itself, and is quite nasty on such things.  My MB has had
troubles as such before.  I know of no workaround, except get a new MB.

><><>< Idrigal of Imladris
----- Original Message -----
From: "Paul Boley" <pboley@home.com>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, 25 December, 2001 11:17 PM
Subject: severe slowdown with 2.4 series w/heavy disk access


> I have been having this problem with the whole 2.4 kernel series.. Under
> heavy disk access, the entire system will slow down and almost all of my
> memory, save 5 megs, gets used up, never to return.  I am currently
> running 2.4.17 on a machine with 416 megs of ram, Duron 750, not
> overclocked.  Cpu temp does not exceed 107 deg F ever, so I don't think
> its a heat issue.  I have an MSI K7T Pro2 motherboard, using the KT133
> chipset.  Anyway, the following is how I can duplicate the problem, in
> about 5 minutes.  I only used mozilla for this because I was working
> with it when I decided to isolate the problem.  Also note this happens
> more than just with tar, and sometimes it happens for no apparent reason
> at all.
>
> *** free and ps -ax, before the slowdown:
>
>              total       used       free     shared    buffers
> cached
> Mem:        417472      30104     387368          0       1264
> 21748
> -/+ buffers/cache:       7092     410380
> Swap:       136544          0     136544
>
>   PID TTY      STAT   TIME COMMAND
>     1 ?        S      0:04 init
>     2 ?        SW     0:00 [keventd]
>     3 ?        SWN    0:00 [ksoftirqd_CPU0]
>     4 ?        SW     0:00 [kswapd]
>     5 ?        SW     0:00 [bdflush]
>     6 ?        SW     0:00 [kupdated]
>    63 ?        S      0:00 /usr/sbin/syslogd
>    66 ?        S      0:00 /usr/sbin/klogd -c 3
>    78 ?        S      0:00 /usr/sbin/atd -b 15 -l 1
>    90 tty1     S      0:00 -bash
>    91 tty2     S      0:00 -bash
>    92 tty3     S      0:00 /sbin/agetty 38400 tty3 linux
>    93 tty4     S      0:00 /sbin/agetty 38400 tty4 linux
>    94 tty5     S      0:00 /sbin/agetty 38400 tty5 linux
>    95 tty6     S      0:00 /sbin/agetty 38400 tty6 linux
>   192 tty2     S      0:00 top
>   200 tty1     R      0:00 ps -ax
>
> *** I then rm -rf'd mozilla, and tar -zxvf mozilla-source-0.9.7.tar.gz,
> *** and immediately after, ran free and ps -ax again.  The system
> started
> *** losing memory and slowing down about 10 seconds into the
> *** decompression.
>
>              total       used       free     shared    buffers
> cached
> Mem:        417472     412192       5280          0      20632
> 315680
> -/+ buffers/cache:      75880     341592
> Swap:       136544          0     136544
>
>   PID TTY      STAT   TIME COMMAND
>     1 ?        S      0:04 init
>     2 ?        SW     0:00 [keventd]
>     3 ?        SWN    0:00 [ksoftirqd_CPU0]
>     4 ?        SW     0:00 [kswapd]
>     5 ?        SW     0:00 [bdflush]
>     6 ?        SW     0:02 [kupdated]
>    63 ?        S      0:00 /usr/sbin/syslogd
>    66 ?        S      0:00 /usr/sbin/klogd -c 3
>    78 ?        S      0:00 /usr/sbin/atd -b 15 -l 1
>    90 tty1     S      0:00 -bash
>    91 tty2     S      0:00 -bash
>    92 tty3     S      0:00 /sbin/agetty 38400 tty3 linux
>    93 tty4     S      0:00 /sbin/agetty 38400 tty4 linux
>    94 tty5     S      0:00 /sbin/agetty 38400 tty5 linux
>    95 tty6     S      0:00 /sbin/agetty 38400 tty6 linux
>   192 tty2     S      0:01 top
>   207 tty1     R      0:00 ps -ax
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  parent reply	other threads:[~2001-12-26  5:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26  5:17 Paul Boley
     [not found] ` <01122609375800.01845@manta>
2001-12-25 10:37   ` Paul Boley
2001-12-26  5:51 ` Idrigal (Eric Rautenkranz) [this message]
2001-12-26 14:58 ` Alan Cox
2001-12-25 10:33   ` Paul Boley
2001-12-26 16:46     ` Calin A. Culianu
2001-12-26 17:36     ` Alan Cox
2001-12-26 19:25 Guillaume Morin

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=OE31AHYoHyYGNTrzLHw0000763c@hotmail.com \
    --to=darklordoflinux@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pboley@home.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

all inboxes | Powered by JetHome®