From: Andrew Morton <akpm@digeo.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: experiences with 2.5.40 on a busy usenet news server
Date: Tue, 08 Oct 2002 02:15:31 -0700 [thread overview]
Message-ID: <3DA2A233.88525FE4@digeo.com> (raw)
In-Reply-To: <anu60s$oev$1@ncc1701.cistron.net>
Miquel van Smoorenburg wrote:
>
> ...
> # free
> total used free shared buffers cached
> Mem: 1033308 1027316 5992 0 836884 29776
> -/+ buffers/cache: 160656 872652
> Swap: 976888 364032 612856
Please always send /proc/meminfo - it's way more informative.
A vmstat trace is also useful.
> No need to swap 364 MB when there's 872 MB still free...
> This makes the machine dogslow. An 'expire' process that
> runs every night normally takes 15 minutes to finish now
> has been running for 10 hours and its still not finished.
It must be doing a ton of IO?
You'll probably find that 2.5.41-mm1 does not swap at all; but
I'd need to see meminfo to know.
next prev parent reply other threads:[~2002-10-08 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 8:46 Miquel van Smoorenburg
2002-10-08 9:11 ` bert hubert
2002-10-08 9:15 ` Andrew Morton [this message]
2002-10-08 9:36 ` Miquel van Smoorenburg
2002-10-08 23:02 ` Miquel van Smoorenburg
2002-10-08 9:22 ` Nick Sanders
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=3DA2A233.88525FE4@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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®