From: Naoki <naoki@valuecommerce.ne.jp>
To: reiserfs-list@namesys.com
Subject: Poor sequential write performance.
Date: Thu, 07 Nov 2002 19:59:55 +0900 [thread overview]
Message-ID: <3DCA47AB.8060008@valuecommerce.ne.jp> (raw)
Why ohh why..
I have an old RedHat 6.2 box with 2.4.2 kernel and an IDE disk. When I
'wc' a file of about 100,000 text lines
it take under a second.
On my new RH 8.0 box with 2.4.18-14 kernel and SCSI disk it takes three
seconds.
This is bizzare. Yes they are under the same load etc etc. They are
both mounted with
noatime / nodirtime. What on earth is going on???
Any help most appreciated.
Look at this -
New machine :
time wc files*
6421 69607 894412 files
38806 420590 5394914 files.1
45227 490197 6289326 total
real 0m3.059s
user 0m2.543s
sys 0m0.064s
Old machine :
time wc files*
18628 201841 2597321 files
46603 505811 6501130 files.1
37122 402985 5201388 files.2
102353 1110637 14299839 total
0.25user 0.04system 0:00.38elapsed 76%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (115major+19minor)pagefaults 0swaps
next reply other threads:[~2002-11-07 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 10:59 Naoki [this message]
2002-11-07 18:09 ` Poor sequential write performance Valdis.Kletnieks
2002-11-08 0:23 ` Getting very interesting - Poor read performance Naoki
2002-11-08 0:48 ` Manuel Krause
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=3DCA47AB.8060008@valuecommerce.ne.jp \
--to=naoki@valuecommerce.ne.jp \
--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.