linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: vmstat output for 2.4.5 fix patch
Date: Fri, 01 Jun 2001 17:01:36 -0400	[thread overview]
Message-ID: <3B1802B0.A0450013@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106011556510.18238-100000@freak.distro.conectiva>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

In case you are interested, here is the "vmstat 3" output from the MySQL
RPM build on alpha.  Kernel is 2.4.5 plus your VM fix patch posted to
lkml a day or two ago.  This does -not- include the balance patch.

The first attach is from a cold boot, and then a build.
The second attach is a second build, which occurs after I rm -rf the
first build, then unpack some random large tarballs (to fill the cache).

/proc/meminfo and /proc/cpuinfo are included at the beginning of each
attach.

MySQL RPM build is mainly interesting because, it uses a mixture of C
and C++ compilers, including a mixture small and medium size files, and
one huge C++ file, which takes up ~300M of VM at the peak of the cc1plus
process size.

About to go test with the balance patch added onto this...

-- 
Jeff Garzik      | Disbelief, that's why you fail.
Building 1024    |
MandrakeSoft     |

[-- Attachment #2: vmstat1.txt.gz --]
[-- Type: application/x-gzip, Size: 8258 bytes --]

[-- Attachment #3: vmstat2.txt.gz --]
[-- Type: application/x-gzip, Size: 8730 bytes --]

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0106011556510.18238-100000@freak.distro.conectiva>
2001-06-01 21:01 ` Jeff Garzik [this message]
2001-06-01 21:04   ` Jeff Garzik

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=3B1802B0.A0450013@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    /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