From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] switching between protocols A and C
Date: Wed, 11 Apr 2007 16:51:40 +0200 [thread overview]
Message-ID: <20070411145140.GA4659@barkeeper1.linbit> (raw)
In-Reply-To: <461CE69A.5020604@dcs.gla.ac.uk>
On Wed, Apr 11, 2007 at 02:46:02PM +0100, Cristian Zamfir wrote:
> Lars Ellenberg wrote:
> >On Wed, Apr 11, 2007 at 01:13:32PM +0100, Cristian Zamfir wrote:
> >>Hi,
> >>
> >>Would it be possible to switch from protocol A to C and vice versa
> >>without disconnecting (for instance detach, switch protocol and
> >>re-attach)?
> >>
> >>This would be useful when alternating between two primaries (only
> >>protocol C can be used) and a primary/secondary configuration where
> >>protocol A may increase write throughput on the primary node.
> >
> >protocol A does _NOT_ increase throughput at all.
> >it _MAY_ reduce latency somewhat sometimes.
>
> I am testing with the bonnie++ benchmark over a 100Mbps link and I get a
> substantial increase for output in the case of protocol A at the expense
> of higher CPU ratio. From what I understand, it would make sense to get
> better throughput from the asynchronous protocol over low quality links.
> Or am I doing something wrong?
and your exact bonnie++ command line is:
--
: Lars Ellenberg Tel +43-1-8178292-0 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe http://www.linbit.com :
__
please use the "List-Reply" function of your email client.
next prev parent reply other threads:[~2007-04-11 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 12:13 [Drbd-dev] switching between protocols A and C Cristian Zamfir
2007-04-11 12:57 ` Lars Ellenberg
2007-04-11 13:46 ` Cristian Zamfir
2007-04-11 14:51 ` Lars Ellenberg [this message]
2007-04-11 15:04 ` Cristian Zamfir
2007-04-11 15:57 ` Lars Ellenberg
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=20070411145140.GA4659@barkeeper1.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
/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