From: Philippe Gramoulle <philippe.gramoulle@mmania.com>
To: Oleg Drokin <green@namesys.com>
Cc: ReiserFS Mailing List <reiserfs-list@namesys.com>
Subject: Re: Speedup patch for 2.4.19-pre6 in bitmap.c
Date: Wed, 10 Apr 2002 20:48:48 +0200 [thread overview]
Message-ID: <20020410204848.N54344@off.aspic.com> (raw)
In-Reply-To: <20020410191356.A22756@namesys.com>; from green@namesys.com on Wed, Apr 10, 2002 at 07:13:56PM +0400
On Wed, Apr 10, 2002 at 07:13:56PM +0400, Oleg Drokin wrote:
> Hello!
>
> On Wed, Apr 10, 2002 at 05:09:19PM +0200, Philippe Gramoulle wrote:
>
> > > So I assume you are negatively surprised, right?
> > > And if you undo the speedup patch only, do you get your numbers back?
> > > Also do you have highmem on for 2.4.19-pre6 kernel?
> > Sorry for the confusion :
> > With 2.4.18 + TCP patch => 10Mb/s
> > Now witout the speedup patch and with a 2.4.19-pre6 + the patches i've listed => 6.32 Mb/s NFS TCP
>
> > That's why i want to give your speedup patch a try !! :o)
>
> Ah. So my question remains, do you have highmem enabled? If you do,
> also try without highmem with and without speedup patches.
Yep , i forgot to answer your question :-(
Yes Higmem is enabled.
As you suggested, i'll try with and without the speedup patch as well as with and
without Highmem.
> Number of peoples raised a question about Andrea Archangelli's patch
> that went into 2.4.19-pre5 to improve I/O throughtput wrt several allocation
> zones.
> I myself see throughtput decrease with highmem on.
As a reminder here is the test with no speedup patch and Highmem on:
time dd if=/dev/zero of=test1 bs=8192 count=25000
25000+0 records in
25000+0 records out
real 0m32.182s
user 0m0.020s
sys 0m1.530s
Now with the speedup patch and still highmem on:
time dd if=/dev/zero of=test2 bs=8192 count=25000
25000+0 records in
25000+0 records out
real 0m41.149s
user 0m0.000s
sys 0m0.920s
With the speedup patch and highmem off:
time dd if=/dev/zero of=zobada bs=8192 count=25000
e25000+0 records in
25000+0 records out
real 0m40.390s
user 0m0.020s
sys 0m1.070s
I'll send the missing test ( without speedup patch and without Highmem) later tonight.
Thanks,
Philippe.
PS: i'll also redo some tests with 2.4.18 +NFS_ALL and try with UDP as well.
next prev parent reply other threads:[~2002-04-10 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 14:55 Speedup patch for 2.4.19-pre6 in bitmap.c Philippe Gramoulle
2002-04-10 15:02 ` Oleg Drokin
2002-04-10 15:09 ` Philippe Gramoulle
2002-04-10 15:13 ` Oleg Drokin
2002-04-10 18:48 ` Philippe Gramoulle [this message]
2002-04-10 19:05 ` Oleg Drokin
2002-04-10 19:09 ` Philippe Gramoulle
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 15:04 wolfgang.glas
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=20020410204848.N54344@off.aspic.com \
--to=philippe.gramoulle@mmania.com \
--cc=green@namesys.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.