From: Andrew Morton <akpm@digeo.com>
To: rwhron@earthlink.net
Cc: piggin@cyberone.com.au, 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 13:39:56 -0800 [thread overview]
Message-ID: <20030124133956.029c4b89.akpm@digeo.com> (raw)
In-Reply-To: <20030124211906.GA15788@rushmore>
rwhron@earthlink.net wrote:
>
> > 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).
Yes, 2.5 sucks at that. Run `top', observe how in 2.4, one qsbench instance
grabs all the CPU time, then exits. The remaining three can now complete
with no swapout at all..
next prev parent reply other threads:[~2003-01-24 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 21:19 rwhron
2003-01-24 21:39 ` Andrew Morton [this message]
-- 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=20030124133956.029c4b89.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=piggin@cyberone.com.au \
--cc=rwhron@earthlink.net \
/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®