public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Saveliev <vs@namesys.com>
To: linux-kernel@vger.kernel.org
Cc: reiserfs-dev@namesys.com
Subject: file write performance drop between 2.5.60 and 2.5.70
Date: Wed, 4 Jun 2003 20:17:53 +0400	[thread overview]
Message-ID: <200306042017.53435.vs@namesys.com> (raw)

Hi

It looks like file write performance dropped somewhere between 2.5.60 and 
2.5.70.
Doing
time dd if=/dev/zero of=file bs=4096 count=60000

on a box with Xeon(TM) CPU 2.40GHz and 1gb of RAM
I get for ext2
2.5.60: 	real	1.42 sys 0.77
2.5.70: 	real 1.73 sys 1.23
for reiserfs
2.5.60: 	real 1.62 sys 1.56
2.5.70: 	real 1.90 sys 1.86

Any ideas of what could cause this drop?

Thanks,
vs



             reply	other threads:[~2003-06-04 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 16:17 Vladimir Saveliev [this message]
2003-06-04 18:02 ` file write performance drop between 2.5.60 and 2.5.70 Felipe Alfaro Solana
2003-06-05 18:37   ` Mike Fedyk
2003-06-05 19:24     ` Felipe Alfaro Solana
2003-06-05 19:27       ` OFFTOPIC: " uaca
2003-06-05  1:52 ` 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=200306042017.53435.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox