From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org
Cc: "J.A. Magallon" <jamagallon@able.es>
Subject: Re: Read this and be ashamed ;) or: Awfull performance loss since 2.4.18 to 2.4.21-pre2
Date: Sun, 22 Dec 2002 23:59:53 +0100 [thread overview]
Message-ID: <200212222352.11560.m.c.p@wolk-project.de> (raw)
In-Reply-To: <20021222222108.GA2482@werewolf.able.es>
On Sunday 22 December 2002 23:21, J.A. Magallon wrote:
Hi J.A.
> On 2002.12.22 Marc-Christian Petersen wrote:
> >On Sunday 22 December 2002 15:38, Marc-Christian Petersen wrote:
> >
> >And hi again ^3,
> >
> >> root@codeman:[/] # uname -r
> >> 2.4.20-rmap15b
> >> root@codeman:[/] # dd if=/dev/zero of=/home/largefile bs=16384
> >> count=131072 131072+0 records in
> >> 131072+0 records out
> >> 2147483648 bytes transferred in 140.460427 seconds (15288887 bytes/sec)
> >
> >root@codeman:[/] # uname -r
> >2.4.20aa1
> >root@codeman:[/] # dd if=/dev/zero of=/home/largefile bs=16384
> > count=131072 131072+0 records in
> >131072+0 records out
> >2147483648 bytes transferred in 286.054011 seconds (7507266 bytes/sec)
>
> Check you timer...
the timer is right.
> Box is a dual PII@400, 950Mb of RAM. FS is ext3.
> So about 83 seconds on -jam2, which is mainly just 2.4.20aa1 with ext3
> fixes. Ah, no special options to ext3 mount (no data=ordered). That's the
> point ?
nono, ordered is default if nothing is specified.
Seems it makes a big difference with DUAL and 1GB RAM. Now with Dual P3 1GHz,
1GB RAM, ext3 ordered mode:
root@codeman:[/] # dd if=/dev/zero of=/home/largefile bs=16384
131072+0 records in
131072+0 records out
2147483648 bytes transferred in 55.741130 seconds (38526016 bytes/sec)
Anyway, the comparison to the different kernels shows up again a better
throughput than with -aa. That is pretty obvious because of the lowlatency
elevator in -aa. But that's not the point. The point is that with
every new kernel release the performance drops. So it shows by dd. Not to
mention the pauses/stops grow up with every new release. It cannot be true
that compared 2.4.18 to 2.4.20 there is a 6mb/s performance loss.
What the hell we can get with $MONSTER-BOX w/o the performance issues ;)
Anyway, that dd call with those options is pretty expensive to mem_load.
I wonder why this doesn't affect contest [tm]. Or am I blind?
ciao, Marc
next prev parent reply other threads:[~2002-12-22 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 13:47 Read this and be ashamed ;) or: Awfull performance loss since 2.4.18 to 2.4.21-pre2 Marc-Christian Petersen
2002-12-22 14:38 ` Marc-Christian Petersen
2002-12-22 14:57 ` Marc-Christian Petersen
2002-12-22 22:21 ` J.A. Magallon
2002-12-22 22:59 ` Marc-Christian Petersen [this message]
2002-12-23 12:03 ` Tomas Szepe
2002-12-23 12:39 ` Marc-Christian Petersen
2002-12-23 12:15 ` Roy Sigurd Karlsbakk
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=200212222352.11560.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=jamagallon@able.es \
--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