public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Bogdan <zoltan.bogdan@t-online.de>
To: linux-kernel@vger.kernel.org
Subject: increasing blocksizes decrease performance in Gbit
Date: 17 Oct 2002 14:38:59 +0200	[thread overview]
Message-ID: <1034858339.13137.3.camel@hermes> (raw)


Hi,


does anyone know about the performace impact whereabouts of different 
blocksizes?

I'm using kernel 2.4.18 on a machine with 512MB Ram and two 3Ware
Escalade 
7850 controllers with an 8-Disk (hardware- )RAID 5  array on each. 

A softraid 0 Array spans  those two Raidarrays.     


While doing some benchmarks over Gbit Network I experianced the
following:
  
Block | Read Lin | Read Rnd | Write Lin
 kB   |  MB/sec  |  MB/sec  |  MB/sec  
------+----------+----------+-----------
   16 |    25.9  |     3.3  |    12.1
   32 |    31.5  |     6.6  |    17.8
  256 |    15.4  |    13.2  |    21.3
 1024 |    13.7  |    20.8  |    21.4

Any clue why the value for linear read decreases when the Blocksizes get
higher?

I thought the contrary to be true.

I apologize if my question I to off topic.


Thanks 
z


                 reply	other threads:[~2002-10-17 12:33 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=1034858339.13137.3.camel@hermes \
    --to=zoltan.bogdan@t-online.de \
    --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