linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 41552] New: Performance of writing and reading from multiple drives decreases by 40% when going from Linux Kernel 2.6.36.4 to 2.6.37 (and beyond)
Date: Mon, 22 Aug 2011 15:20:41 GMT	[thread overview]
Message-ID: <bug-41552-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=41552

           Summary: Performance of writing and reading from multiple
                    drives decreases by 40% when going from Linux Kernel
                    2.6.36.4 to 2.6.37 (and beyond)
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 2.6.37
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
        AssignedTo: linux-scsi@vger.kernel.org
        ReportedBy: mpete_06@hotmail.com
        Regression: No


We have an application that will write and read from every sector on a drive. 
The application can perform these tasks on multiple drives at the same time. 
It is designed to run on top of the Linux Kernel, which we periodically update
so that we can get the latest device drivers.  When performing the last update
from 2.6.33.2 to 2.6.37, we found that the performance of a set of drives
decreased by some 40% (took 3 hours and 11 minutes to write and read from 5
drives on 2.6.37 versus 2 hours and 12 minutes on 2.6.33.3).  I was able to
determine that the issue was in the 2.6.37 Kernel as I was able to run it with
the 2.6.36.4 kernel, and it had the better performance.   After seeing that I/O
throttling was introduced in the 2.6.37 Kernel, I naturally suspected that. 
However, by default, all the throttling was turned off (I attached the actual
.config that was used to build the kernel).  I then tried to turn on the
throttling and set it to a high number to see what would happen.  When I did
that, I was able to reduce the time from 3 hours and 11 minutes to 2 hours and
50 minutes.  There seems to be something there that changed that is impacting
performance on multiple drives.  When we do this same test with only one drive,
the performance is identical between the systems.  This issue still occurs on
Kernel 3.0.2.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-08-22 15:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 15:20 bugzilla-daemon [this message]
2011-08-22 15:21 ` [Bug 41552] Performance of writing and reading from multiple drives decreases by 40% when going from Linux Kernel 2.6.36.4 to 2.6.37 (and beyond) bugzilla-daemon
2011-08-22 15:22 ` bugzilla-daemon
2011-08-22 15:22 ` bugzilla-daemon
2011-08-22 19:25 ` bugzilla-daemon
2011-08-22 19:25 ` bugzilla-daemon
2011-08-22 20:21 ` bugzilla-daemon
2011-08-22 20:21 ` bugzilla-daemon
2011-08-22 20:24 ` bugzilla-daemon
2011-08-22 21:02 ` bugzilla-daemon
2011-08-22 21:07 ` bugzilla-daemon
2011-08-23 14:00   ` James Bottomley
2011-08-23 14:38 ` bugzilla-daemon
2011-08-24 20:46 ` bugzilla-daemon
2011-08-25 21:02 ` bugzilla-daemon
2012-08-30 10:41 ` bugzilla-daemon

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=bug-41552-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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).