public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christopher Zimmerman <zim@av.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5 VM
Date: Thu, 31 May 2001 16:58:22 -0700	[thread overview]
Message-ID: <3B16DA9E.39983944@av.com> (raw)
In-Reply-To: <3B16C9A8.7090402@digitalme.com> <3B16CCE9.64597F2E@av.com> <3B16DA37.206FF579@av.com>

Actually I take everything back.  I've been testing on linux-2.4.5-xfs and seen
major improvements.

-zim

Christopher Zimmerman wrote:

> Christopher Zimmerman wrote:
>
> > "Trever L. Adams" wrote:
> >
> > > In my opinion 2.4.x is NOT ready for primetime.  The VM has been getting
> > > worse since 2.4.0, I believe.  Definitely since and including 2.4.3.  I
> > > cannot even edit a few images in gimp where the entire working set used
> > > to fit entirely in memory.  The system now locks in some loop (SAK still
> > > works).
> > >
> > > FILE CACHING IS BROKEN.  I don't care who says what, by the time swap is
> > > half filled, it is time to start throwing away simple caches.  Not wait
> > > until there is no more memory free and then lock in an infinite loop.
> > >
> > > My system has 128 Meg of Swap and RAM.
> > >
> > > Trever Adams
> > >
> > > -
> > > 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/
> >
> > I've found that with the latest kernel release (2.4.5) VM performance has
> > been greatly improved.  kswapd and bdflush no longer use 200% of my cpu
> > cycles when simply doing a dd bs=1024 count=8388608 if=/dev/zero
> > of=test.file.  All of my test systems remain responsive with about 180% cpu
> > available.  These systems are running software RAID and 3ware IDE raid with
> > 2GB of memory and 4GB swap.  Have you tried 2.4.5?
> >
> > -zim
> >
> > Christopher Zimmerman
> > AltaVista Company
> >
> > -
> > 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/


  reply	other threads:[~2001-06-01  0:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-31 22:46 2.4.5 VM Trever L. Adams
2001-05-31 22:49 ` Alan Cox
2001-05-31 22:56   ` Trever L. Adams
2001-05-31 22:57     ` Alan Cox
2001-06-01  4:27       ` Billy Harvey
2001-06-01  8:29   ` Marcin Kowalski
2001-06-01  8:43     ` David Rees
2001-06-01 15:48   ` Russell Leighton
2001-05-31 22:59 ` Christopher Zimmerman
2001-05-31 23:40   ` Trever L. Adams
2001-05-31 23:56   ` Christopher Zimmerman
2001-05-31 23:58     ` Christopher Zimmerman [this message]
     [not found] <Pine.LNX.4.10.10106011028150.6653-100000@webman.medikredit.co.>
2001-06-01  9:27 ` Marcin Kowalski
2001-06-01 14:42   ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2001-06-01 17:15 Miquel Colom Piza
2001-06-01 17:53 ` Ken Brownfield
2001-06-05 11:18 Martin.Knoblauch
2001-06-05 17:20 ` Alan Cox
2001-06-06  7:06   ` Martin.Knoblauch
2001-06-06  7:42     ` Christian Bornträger
2001-06-06  7:51     ` Alan Cox
2001-06-06  7:45   ` Jonathan Morton

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=3B16DA9E.39983944@av.com \
    --to=zim@av.com \
    --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