From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Cc: andrea@suse.de
Subject: Slabinfo memory usage after big box benchmarks
Date: Sat, 25 May 2002 14:24:09 -0400 [thread overview]
Message-ID: <20020525142409.A323@rushmore> (raw)
I don't know if this is related to the negative
dentry thread or not. After running various
benchmarks on quad Xeon with 3.75 GB RAM,
there are some big differences in slab size.
inode_cache and dentry_cache have the biggest
difference between kernels.
total slab size inode_cache
2.4.19-pre7-rmap13 45.9 MB 9.9 MB
2.4.19-pre8 278.0 MB 202.8 MB
2.4.19-pre8-aa2 306.1 MB 233.9 MB
2.4.19-pre8-ac4 44.3 MB 4.5 MB
2.4.19-pre8-jam2 263.9 MB 182.1 MB
The benchmarks create a million or more temp
files during the run. Updatedb runs several
times too.
bonnie++ is one of the benches that creates a lot
of files. On runs with vastly different "number
of files to create", there was little difference
in slabinfo memory usage on 2.4.19-pre8-jam2.
More slabinfo detail at:
http://home.earthlink.net/~rwhron/kernel/bigbox/slabinfo.txt
Script to create slabinfo.txt in url above:
http://home.earthlink.net/~rwhron/kernel/bigbox/si_sum
Big box benchmarks:
http://home.earthlink.net/~rwhron/kernel/bigbox.html
--
Randy Hron
reply other threads:[~2002-05-25 18:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020525142409.A323@rushmore \
--to=rwhron@earthlink.net \
--cc=andrea@suse.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