From: Stephan von Krawczynski <skraw@ithnet.com>
To: Klaus Meyer <k.meyer@m3its.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: highmem=system killer, 2.2.17=performance killer ?
Date: Tue, 15 Jan 2002 17:49:18 +0100 [thread overview]
Message-ID: <20020115174918.11a3bafc.skraw@ithnet.com> (raw)
In-Reply-To: <3C445BFC.E373EA04@m3its.de>
In-Reply-To: <3C439E6D.B2B8C5B8@m3its.de> <20020115160018.18793569.skraw@ithnet.com> <3C445BFC.E373EA04@m3its.de>
On Tue, 15 Jan 2002 17:42:36 +0100
Klaus Meyer <k.meyer@m3its.de> wrote:
> As I just took a look on the output of cat /proc/meminfo i got the idea
> that i'll increase the pysical swap space. (136M before that means >
> highmem).
> astonishing (using Suse kernel 2.4.16): after an increase to 2GB swap
> and
> using 1,5GB of mem the system runs quit a longer time with a good
> performance,
> but starting the copy process leads also to a slow down of the machine.
> Finally i could see that kupdated is suffering.
I was already tempted to suggest you turn off swap completely, as 136 MB in a 2
GB box are somehow useless anyways. I know, I have the same setup (256MB swap).
As this could work without boot, willing to give it a try? Anyway I would very
much suggest to use -pre3.
Regards,
Stephan
next prev parent reply other threads:[~2002-01-15 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 3:13 highmem=system killer, 2.2.17=performance killer ? Klaus Meyer
2002-01-15 15:00 ` Stephan von Krawczynski
2002-01-15 16:42 ` Klaus Meyer
2002-01-15 16:49 ` Stephan von Krawczynski [this message]
2002-01-18 2:04 ` Klaus Meyer
2002-01-18 4:56 ` Bill Davidsen
2002-01-18 14:34 ` Klaus Meyer
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 14:46 rwhron
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=20020115174918.11a3bafc.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=k.meyer@m3its.de \
--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