All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allan Sandfeld <linux@sneulv.dk>
To: linux-kernel@vger.kernel.org
Cc: Stephan von Krawczynski <skraw@ithnet.com>
Subject: Re: 2.4.13pre3aa1
Date: Tue, 16 Oct 2001 15:55:27 +0200	[thread overview]
Message-ID: <E15tUgv-0000Oh-00@Princess> (raw)
In-Reply-To: <20011016110708.D2380@athlon.random> <E15tTMq-0000E6-00@Princess> <20011016152126.01d58180.skraw@ithnet.com>
In-Reply-To: <20011016152126.01d58180.skraw@ithnet.com>

On Tuesday 16 October 2001 15:21, you wrote:
>
> On my system I cannot see anything the like. Look at the execution time.
> Ok, I must admit: I do not use brain-dead K stuff (warning: this is a very
> personal opinion, don't flame me here :-).
>
> What does your setup look like? Have you ever tested without K?
>
No, I havent tried it without K. The system is quite responsive if I only run 
updatedb, and swap around in either text-linux or a simple X setup. When 
looking closer at the problem, it is the combination of running kmail with 
HUGE folders (think linux-kernel archive), apt-get and anacron that thrashes 
the system. All of these have a "relative" low impact when running alone or 
two and two.
It might be "what you expect" abusing the system like that. But as I said, it 
is not a problem in 2.4.11-pre1 and 2.4.12-ac3. 

Princess:/home# cat /proc/meminfo
        total:    used:    free:  shared: buffers:  cached:
Mem:  196304896 192466944  3837952        0  1327104 33628160
Swap: 255426560 64491520 190935040
MemTotal:       191704 kB
MemFree:          3748 kB
MemShared:           0 kB
Buffers:          1296 kB
Cached:          28196 kB
SwapCached:       4644 kB
Active:          23344 kB
Inactive:        10792 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       191704 kB
LowFree:          3748 kB
SwapTotal:      249440 kB
SwapFree:       186460 kB

Princess:/proc# uname -r
2.4.13-pre2

Princess:/proc# df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda3             18975356   9843804   8167652  55% /
/dev/hda1                 7318      7241         0 100% /boot

 15:52:56 up  1:03,  2 users,  load average: 3.44, 3.95, 3.16
90 processes: 86 sleeping, 2 running, 2 zombie, 0 stopped
CPU states:  23.7% user,   3.4% system,   0.0% nice,  73.0% idle
Mem:    191704K total,   188024K used,     3680K free,     2652K buffers
Swap:   249440K total,    61744K used,   187696K free,    21268K cached


Does all this help you?

Notice this is not worst case, just what I could reproduce by starting 
updatedb and checksecurity while answering your mail. Switchtime from desktop 
to desktop is 1 minute.

`Allan

  reply	other threads:[~2001-10-16 13:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16  9:07 2.4.13pre3aa1 Andrea Arcangeli
2001-10-16 12:30 ` 2.4.13pre3aa1 Allan Sandfeld
2001-10-16 13:21   ` 2.4.13pre3aa1 Stephan von Krawczynski
2001-10-16 13:55     ` Allan Sandfeld [this message]
2001-10-16 18:38       ` 2.4.13pre3aa1 Stephan von Krawczynski
2001-10-17  8:55         ` 2.4.13pre3aa1 Allan Sandfeld
2001-10-16 14:26     ` 2.4.13pre3aa1 Allan Sandfeld

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=E15tUgv-0000Oh-00@Princess \
    --to=linux@sneulv.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.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 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.