mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephan van Hienen <raid@a2000.nu>
To: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: bernard@biesterbos.nl
Subject: tuning disk on 3ware /performance problem
Date: Sun, 6 Apr 2003 16:20:33 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0304061251190.8636@ddx.a2000.nu> (raw)

same disk (WD1800BB) on different controllers

----------
on intel u100/promise U100 :

/dev/hde:
 Timing buffer-cache reads:   128 MB in  0.28 seconds =457.14 MB/sec
 Timing buffered disk reads:  64 MB in  1.37 seconds = 46.72 MB/sec

Version 1.02c       ------Sequential Output------ --Sequential Input-
--Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP
/sec %CP
storage.a2000.nu 1G 22364  96 42206  13 15897   6 22634  91 44019  10
252.1   0
                    ------Sequential Create------ --------Random
Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read---
-Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
/sec %CP
                 16  3658  99 +++++ +++ +++++ +++  3757  99 +++++ +++
9681 100
storage.a2000.nu,1G,22364,96,42206,13,15897,6,22634,91,44019,10,252.1,0,16,3658,99,+++++,+++,+++++,+++,3757,99,+++++,+++,9681,100
----------
# hdparm -v /dev/hde

/dev/hde:
 multcount    = 16 (on)
 IO_support   =  3 (32-bit w/sync)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 21889/255/63, sectors = 351651888, start = 0


----------
on 3ware (7850) :

/dev/sdb:
 Timing buffer-cache reads:   128 MB in  0.28 seconds =457.14 MB/sec
 Timing buffered disk reads:  64 MB in  1.70 seconds = 37.65 MB/sec


Version 1.02c       ------Sequential Output------ --Sequential Input-
--Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP
/sec %CP
storage.a2000.nu 1G 22151  94 67312  18 20152   8 22315  90 38488   9
260.4   0
                    ------Sequential Create------ --------Random
Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read---
-Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
/sec %CP
                 16  3706  99 +++++ +++ +++++ +++  3895  99 +++++ +++
9686  99
storage.a2000.nu,1G,22151,94,67312,18,20152,8,22315,90,38488,9,260.4,0,16,3706,99,+++++,+++,+++++,+++,3895,99,+++++,+++,9686,99
----------
]# hdparm -v /dev/sdb

/dev/sdb:
 readonly     =  0 (off)
 geometry     = 21889/255/63, sectors = 351651888, start = 0


Is there anything i can do to tune the drives connected to he 3ware
controller ? (37MB/sec vs 43MB/sec)
(and why is the seq. output block 65MB/sec on the 3ware vs 41MB/sec on
'ide controllers')


             reply	other threads:[~2003-04-06 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06 14:20 Stephan van Hienen [this message]
2003-04-06 15:29 Chuck Ebbert
2003-04-06 15:56 ` Stephan van Hienen
2003-04-06 18:55 ` dean gaudet
2003-04-06 18:58   ` dean gaudet

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=Pine.LNX.4.53.0304061251190.8636@ddx.a2000.nu \
    --to=raid@a2000.nu \
    --cc=bernard@biesterbos.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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

all inboxes | Powered by JetHome®