public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: linux-kernel@vger.kernel.org
Subject: ext3 reservation seems to cause major slowdown in synctest in 2.6.10-rc2 vs 2.6.9
Date: Mon, 15 Nov 2004 14:33:25 +0800	[thread overview]
Message-ID: <20041115063325.GA31537@outblaze.com> (raw)

I have a P3-500 box /384 MB ram and 2 scsi disks (sda and sdb).
OS is on sda and test partions is on sdb
aic7xxx driver 
Using anticipatory schedulor with a tag_depth of 4 (this is set via
modules.conf)
options aic7xxx aic7xxx=global_tag_depth:4

/dev/sdb1 is created with ext3 and htree is enabled. Mounted as /htree

synctest obtained from here (synctest tries to simulate an MTA
behaviour)

http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz

I run the following commands on both 2.6.9 and 2.6.10-rc2

/usr/bin/time -p ./synctest -fu -t 100 -p1 -n1 /htree/nfsexport

timing results

2.6.9 

real 57.35
user 1.37
sys 14.26

2.6.10-rc2

real 86.83
user 1.32
sys 14.02

Mounting with noreservation gives the following numbers

real 58.77
user 1.46
sys 14.48


                 reply	other threads:[~2004-11-15  6:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20041115063325.GA31537@outblaze.com \
    --to=yusufg@outblaze.com \
    --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