linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matus Kocka <mkocka@redhat.com>
To: linux-fsdevel@vger.kernel.org
Subject: Regression ~7% write, 3.17.1 vs 3.18.0rc5
Date: Fri, 28 Nov 2014 18:45:37 +0100	[thread overview]
Message-ID: <5478B4C1.5060203@redhat.com> (raw)

Hello,

we see the ~7% regression in the initial WRITE on xfs in in-cache mode 
by IOZONE test
between 3.17.1-306.el7 and  3.18.0-0.rc5.git0.1.el7 (respectively 
3.18.0-0.rc3.git0.2.el7)

By in-cache mode we mean that file fits into the OS cache.
For big file-sizes >4GiB (out of cache mode) there is no performance drop.

[Files: 
https://www.dropbox.com/sh/2sx0ejt73n4idcp/AAA0nYhZTDAMGigJ-B5yqTwga?dl=0]

1, Firstly, (xfs_SATA.pdf) we see the ~7% regression in the in-cache
IOZONE test on 1 TB SATA disk with cfq io-elevator,

2, We also see it (xfs_write.pdf) using same in-cache test on the
fast pci SSD disk (RealSSD P320h 350GB)

3, We have tried direct-io tests on the same pci SSD with no regression 
(directio.pdf)

It seems that this regression is related to cache since DIRECT IO and 
out-of-cache tests
   do not have the regression. Also, rewrite test does not show any 
regression.

Would somebody from the developers be interested to look into it and try 
to hunt down this bug?
We can provide more details regarding our testing methodology but we 
have neither capacity nor
expertise to debug it ourselves.

-- 
Matus Kocka

Quality Assurance Associate
Red Hat Czech s.r.o.
Purkyňova 99/71, 612 45, Brno, Czech Republic

    tel.: +420 532 294 793
direct: 8262793
   email: mkocka [at] redhat.com


--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-11-28 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 17:45 Matus Kocka [this message]
2014-11-28 21:05 ` Regression ~7% write, 3.17.1 vs 3.18.0rc5 Dave Chinner

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=5478B4C1.5060203@redhat.com \
    --to=mkocka@redhat.com \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).