All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 849] New: [perf][tiobench] tiobench sequential write degrades in 2.5.72-bk2
Date: Tue, 24 Jun 2003 15:28:04 -0700	[thread overview]
Message-ID: <194570000.1056493684@flay> (raw)

http://bugme.osdl.org/show_bug.cgi?id=849

           Summary: [perf][tiobench] tiobench sequential write degrades in
                    2.5.72-bk2
    Kernel Version: 2.5.72-bk2
            Status: NEW
          Severity: high
             Owner: akpm@digeo.com
         Submitter: slpratt@us.ibm.com


Hardware Environment: 8way 900mhz adaptec scsi drives

Software Environment: sles8.0 + 2.5 kernel

Problem Description:

tiobench sequential write throughput drops between 2.5.72-bk1 and 2.5.72-bk2 for
multi threaded IO.

                                 tolerance = 1.00 + 5.00% of 2.5.72-bk1
             2.5.72-bk1   2.5.72-bk2
    Theads      MBs/sec      MBs/sec    %diff         diff    tolerance
---------- ------------ ------------ -------- ------------ ------------
         1        43.27        42.90    -0.86        -0.37         3.16 
        16        11.86         4.35   -63.32        -7.51         1.59  * 
        64         3.95         2.50   -36.71        -1.45         1.20  * 


Results:Sequential Write CPU (Graph)
 
                                 tolerance = 1.00 + 3.00% of 2.5.72-bk1
             2.5.72-bk1   2.5.72-bk2
    Theads         %CPU         %CPU    %diff         diff    tolerance
---------- ------------ ------------ -------- ------------ ------------
         1       52.87%       50.78%    -3.95        -2.09         2.59 
        16       127.6%       49.03%   -61.58       -78.57         4.83  * 
        64       37.51%       22.15%   -40.95       -15.36         2.13  * 


http://ltcperf.ncsa.uiuc.edu/data/2.5.72-bk2/2.5.72-bk1-vs-2.5.72-bk2/
Folloow link for tiobench.ext3 summary report and full results.

Steps to reproduce:
tiobench  --dir /mnt/tmp --block 4096 --size 600 --numruns 10 --threads 16


                 reply	other threads:[~2003-06-24 22:25 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=194570000.1056493684@flay \
    --to=mbligh@aracnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.