public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: fio rand read/write regression with 2.6.32-rc3
Date: Sat, 10 Oct 2009 13:48:44 +0800	[thread overview]
Message-ID: <1255153724.25078.68.camel@ymzhang> (raw)

Comparing with 2.6.23-rc1's result, fio rand read write has regression
on my 2*4 core stoakley machine (8GB memory) with a JBOD of 12 disks.

Every disk has 8 1-GB files. Start 8 sub-processes per disk and every
process random chooses a file on the disk to do 36 times of file read or
write on the file and then choose another file.


fio_mmap_rand_read_4k regresion is about 35%.
Bisect down to patch:
1d2235152dc745c6d94bedb550fea84cffdbf768 is first bad commit
commit 1d2235152dc745c6d94bedb550fea84cffdbf768
Author: Jens Axboe <jens.axboe@oracle.com>
Date:   Fri Oct 2 19:27:04 2009 +0200

    cfq-iosched: add a knob for desktop interactiveness


After I revert the patch against 2.6.23-rc3, fio_mmap_rand_read_4k regression
disappears.

fio_mmap_randrw_4k has less than 20% regression and reverting the patch
could restore performance.

On another stoakley machine with another JBOD, we see the similiar regression.

ffsb rand read/write has a bigger regression and reverting the patch
could restore performance.

Yanmin



             reply	other threads:[~2009-10-10  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10  5:48 Zhang, Yanmin [this message]
2009-10-10  8:01 ` fio rand read/write regression with 2.6.32-rc3 Jens Axboe
2009-10-10  8:02   ` Jens Axboe
2009-10-10  9:47     ` Zhang, Yanmin
2009-10-10  9:52   ` Zhang, Yanmin
2009-10-11  8:23     ` Corrado Zoccolo
2009-10-12  5:50       ` Zhang, Yanmin

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=1255153724.25078.68.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.com \
    --cc=jens.axboe@oracle.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