From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: -b vs. -n
Date: Fri, 30 Jan 2009 12:59:25 +0000 [thread overview]
Message-ID: <4982F9AD.3020408@hp.com> (raw)
In-Reply-To: <49821F8D.4050207@hp.com>
Jens Axboe wrote:
> On Thu, Jan 29 2009, Alan D. Brunelle wrote:
>> Has anybody experimented with increasing the _number_ of buffers rather
>> than the _size_ of the buffers when confronted with drops? I'm finding
>> on a large(ish) system that it is better to have lots of small buffers
>> handled by relay rather than fewer larger buffers. In my particular case:
>>
>> 16 CPUs
>> 96 devices
>> running some dd's against all the devices...
>>
>> -b 1024 or -b 2048 still results in drops
>>
>> but:
>>
>> -n 512 -b 16 allows things to run smoother.
>>
>> I _think_ this may have to do with the way relay reports POLLIN: it does
>> it only when a buffer switch happens as opposed to when there is data
>> ready. Need to look at this some more, but just wondering if others out
>> there have found similar things in their testing...
>
> That's interesting. The reason why I exposed both parameters was mainly
> that I didn't have the equipment to do adequate testing on what would be
> the best setup for this. So perhaps we can change the README to reflect
> that it is usually better to bump the number of buffers instead of the
> size, if you run into overflow problems?
>
It's not clear - still running tests. [I know for SMALLER numbers of
disks increasing the buffers has worked just fine.] I'm still fighting
(part time) with version 2.0 of blktrace, so _that_ may have something
to do with it! :-)
Alan
next prev parent reply other threads:[~2009-01-30 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 21:28 -b vs. -n Alan D. Brunelle
2009-01-30 7:42 ` Jens Axboe
2009-01-30 12:59 ` Alan D. Brunelle [this message]
2009-02-02 14:09 ` Alan D. Brunelle
2009-02-02 20:53 ` Alan D. Brunelle
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=4982F9AD.3020408@hp.com \
--to=alan.brunelle@hp.com \
--cc=linux-btrace@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).