mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: experiences beyond 4 GB RAM with 2.4.22
Date: Tue, 9 Sep 2003 14:25:47 +0200	[thread overview]
Message-ID: <20030909122547.GN21086@dualathlon.random> (raw)
In-Reply-To: <20030909110112.4d634896.skraw@ithnet.com>

On Tue, Sep 09, 2003 at 11:01:12AM +0200, Stephan von Krawczynski wrote:
> Hello,
> 
> lately I upgraded my testbox from 2 to 6 GB ram and found out some oddities I
> would like to hear your opinions.
> The box ran flawlessly and performant with 2 GB - was in fact a real joy.
> After upgrading the ram and recompiling kernel 2.4.22 with support for 64 GB I
> noticed:
> 
> 1) nfs clients see timeouts again, like
> 
> Sep  9 03:37:35 clienta kernel: nfs: server 192.168.1.1 not responding, still
> trying
> Sep  9 03:37:35 clienta kernel: nfs: server 192.168.1.1 OK
> Sep  9 03:37:35 clienta kernel: nfs: server 192.168.1.1 not responding, still
> trying
> Sep  9 03:37:35 clienta kernel: nfs: server 192.168.1.1 OK
> Sep  9 03:41:13 clienta kernel: nfs: server 192.168.1.1 not responding, still
> trying
> Sep  9 03:41:13 clienta kernel: nfs: server 192.168.1.1 OK
> 
> Both are 2.4.22. 192.168.1.1 is the testbox. I saw those with 2GB, but could
> fix it through more nfs-daemons and
> 
>         echo 2097152 >/proc/sys/net/core/rmem_max
>         echo 2097152 >/proc/sys/net/core/wmem_max
> 
> Are these values too small for 6 GB?
> 
> 2) Box is very slow, kswapd looks very active during tar of a local harddisk.
> Interactivity is really bad. Seems vm has a high time looking for free or
> usable pages. Compared to 2 GB the behaviour is unbelievably bad.
> 
> 3) Network performance has a remarkable dropdown during above tar. In fact
> doing simple pings every few minutes shows that quite a lot of them are simply
> dropped, never make it over the ethernet.
> 
> I am really astonished about this. Can some kind soul give me hints or maybe
> patches to try?

for the vm issues my suggestion is to try again with 2.4.22aa1.

Andrea

/*
 * If you refuse to depend on closed software for a critical
 * part of your business, these links may be useful:
 *
 * rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.5/
 * rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.4/
 * http://www.cobite.com/cvsps/
 *
 * svn://svn.kernel.org/linux-2.6/trunk
 * svn://svn.kernel.org/linux-2.4/trunk
 */

  reply	other threads:[~2003-09-09 12:24 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09  9:01 Stephan von Krawczynski
2003-09-09 12:25 ` Andrea Arcangeli [this message]
2003-09-12  2:46 ` Neil Brown
2003-09-12  6:54   ` Stephan von Krawczynski
2003-09-12  7:11     ` Jens Axboe
2003-09-12  7:53     ` Mike Fedyk
2003-09-15 22:01     ` Marcelo Tosatti
2003-09-16  8:21       ` Stephan von Krawczynski
2003-09-16 12:05         ` Stephan von Krawczynski
2003-09-16 13:11         ` Marcelo Tosatti
2003-09-16 13:36           ` Stephan von Krawczynski
2003-09-16 13:55             ` Richard B. Johnson
2003-09-16 14:13               ` Stephan von Krawczynski
2003-09-16 14:33             ` Marcelo Tosatti
2003-09-16 14:36               ` Stephan von Krawczynski
2003-09-16 14:36             ` Alan Cox
2003-09-16 15:20               ` Stephan von Krawczynski
2003-09-16 15:29                 ` Alan Cox
2003-09-16 15:49                   ` Timothy Miller
2003-09-16 16:17                     ` Stephan von Krawczynski
2003-09-16 19:58                   ` Olivier Galibert
2003-09-17 15:10                     ` Alan Cox
2003-09-17 19:19                       ` Jens Axboe
2003-09-17 19:30                         ` Marcelo Tosatti
2003-09-17 22:18                           ` Stephan von Krawczynski
2003-09-18  7:08                           ` Jens Axboe
2003-09-18  7:12                             ` Jens Axboe
2003-09-18 11:22                               ` Stephan von Krawczynski
2003-09-18 15:05                             ` William Lee Irwin III
2003-09-16 17:10               ` Pavel Machek
2003-09-16 19:53                 ` Olivier Galibert
2003-09-16 20:04                   ` Pavel Machek
2003-09-16 21:16                   ` Marcelo Tosatti
2003-09-16 21:23                     ` Olivier Galibert
2003-09-17 11:14                       ` Stephan von Krawczynski
2003-09-17 13:08                         ` Olivier Galibert
2003-09-18  9:58                           ` Olivier Galibert
2003-09-18 10:13                             ` Stephan von Krawczynski
2003-09-18 11:22                               ` Olivier Galibert
2003-09-17  6:41               ` Rogier Wolff
2003-09-17 10:26                 ` Jens Axboe
2003-09-17 10:42                   ` Rogier Wolff
2003-09-17 10:53                     ` Jens Axboe
2003-09-17 19:19                   ` Pavel Machek
2003-09-18 11:39                     ` Rogier Wolff
2003-09-18 12:13                       ` Rogier Wolff
2003-09-16 15:22             ` Timothy Miller
2003-09-16 15:29             ` Martin J. Bligh

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=20030909122547.GN21086@dualathlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --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 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®