From: Simone Piunno <simone.piunno@wseurope.com>
To: Jens Axboe <axboe@suse.de>
Cc: Fabio Coatti <fabio.coatti@wseurope.com>,
Baruch Even <baruch@ev-en.org>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel@vger.kernel.org
Subject: Re: bonnie++ uninterruptible under heavy I/O load
Date: Fri, 11 Mar 2005 17:24:44 +0100 [thread overview]
Message-ID: <200503111724.44296.simone.piunno@wseurope.com> (raw)
In-Reply-To: <20050311160048.GM28188@suse.de>
Alle 17:00, venerdì 11 marzo 2005, Jens Axboe ha scritto:
> > It was after running bonnie++.
>
> Are you sure? It lists only 190 commands run since it initialized,
> that's basically nothing.
Yes I'm sure!
Isn't this number the MAX value ever samplef for "Current # commands on
controller"? It doesn't seem to be the counter of how many commands were
processed since start.
To doublecheck, I're run bonnie one more time.
This one was taken while bonnie was running:
cciss0: HP Smart Array 5i Controller
Board ID: 0x40800e11
Firmware Version: 2.56
IRQ: 18
Logical drives: 1
Current Q depth: 0
Current # commands on controller: 132
Max Q depth since init: 147
Max # commands on controller since init: 190
Max SG entries since init: 31
rereading the file, the only moving number was "Current # commands on
controller", basically oscillating between 10 and 150.
> 6 was the highest depth, should not be enough to cause serious latency
> issues unless it was constantly at 6.
As you see, after more runs Max Q raised to 147, but I'm sure it was 6 after
that first run, and in that 1st run responsiveness was already sluggish.
Anyway, I wouldn't focus too much on CCISS, cause the only thing that's
specific of this hardware is the long delay killing bonnie.
Bad responsiveness has been found almost everywhere else.
--
Simone Piunno, chief architect
Wireless Solutions SPA - DADA group
Europe HQ, via Castiglione 25 Bologna
web:www.dada-ws.com tel:+39512966811 fax:+39512966800
next prev parent reply other threads:[~2005-03-11 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 11:08 Simone Piunno
2005-03-11 11:35 ` Denis Vlasenko
2005-03-11 13:20 ` Fabio Coatti
2005-03-11 13:29 ` Baruch Even
2005-03-11 14:14 ` Simone Piunno
2005-03-11 15:16 ` Jens Axboe
2005-03-11 15:50 ` Fabio Coatti
2005-03-11 15:54 ` Jens Axboe
2005-03-11 15:58 ` Simone Piunno
2005-03-11 16:00 ` Jens Axboe
2005-03-11 16:24 ` Simone Piunno [this message]
2005-03-11 14:24 Christian Guggenberger
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=200503111724.44296.simone.piunno@wseurope.com \
--to=simone.piunno@wseurope.com \
--cc=axboe@suse.de \
--cc=baruch@ev-en.org \
--cc=fabio.coatti@wseurope.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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®