From: rwhron@earthlink.net
To: akpm@digeo.com, piggin@cyberone.com.au
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: big ext3 sequential write improvement in 2.5.51-mm1 gone in 2.5.53-mm1?
Date: Fri, 24 Jan 2003 16:19:06 -0500 [thread overview]
Message-ID: <20030124211906.GA15788@rushmore> (raw)
> qsbench isn't really a thing which should be optimised for.
The way I run qsbench simulates an uncommon workload.
> It is important to specify how much memory you have, and how you are
> invoking qsbench.
There is 3.75 GB of ram. I grab MemTotal from /proc/meminfo, and run
4 qsbench processes. Each qsbench uses 30% of MemTotal (1089 megs).
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2003-01-24 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 21:19 rwhron [this message]
2003-01-24 21:39 ` big ext3 sequential write improvement in 2.5.51-mm1 gone in 2.5.53-mm1? Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 1:26 rwhron
2003-01-24 2:10 ` Andrew Morton
2003-01-24 2:33 ` Nick Piggin
2003-01-16 1:50 rwhron
2003-01-16 6:31 ` Andrew 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=20030124211906.GA15788@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=piggin@cyberone.com.au \
/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