public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: David Teigland <teigland@redhat.com>,
	Wim Coekaerts <wim.coekaerts@oracle.com>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 0/7] dlm: overview
Date: Thu, 28 Apr 2005 16:36:19 +0200	[thread overview]
Message-ID: <20050428143619.GZ21645@marowsky-bree.de> (raw)
In-Reply-To: <20050427181245.GB938@ca-server1.us.oracle.com>

On 2005-04-27T11:12:45, Mark Fasheh <mark.fasheh@oracle.com> wrote:

> The short answer is no but that we're collecting them. Right now, I can say
> that if you take our whole stack into consideration OCFS2 for things like
> kernel untars and builds (a common test over here), is typically almost as
> fast as ext3 (single node obviously) even when we have a second or third
> node mounted.

Well, agreed that's great, but that seems to imply just generic sane
design: Why should the presence of another node (which does nothing, or
not with overlapping objects on disk) cause any substantial slowdown?

Admittedly we seem to be really short of meaningful benchmarks for DLMs
and/or clustering filesystems...

Hey. Wait. Benchmarks. Scalability issues. No real coding involved.
Anyone from OSDL listening?  ;-)

> As far as specific DLM timings go, we're in the process of collecting them.

Perfect.

> As you know, lately we have been deep in a process of stabilizing things :)

Yes, but this also would be a great time to identify real performance
bugs before shipping - so consider it as part of stress tesing ;-)

> While we have collected timings independent of the FS in the past, we
> haven't done that recently enough that I'd feel comfortable posting it.

Understood.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business


  reply	other threads:[~2005-04-28 14:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 15:11 [PATCH 0/7] dlm: overview David Teigland
2005-04-25 20:39 ` Wim Coekaerts
2005-04-25 21:09   ` Lars Marowsky-Bree
2005-04-26  5:30     ` Daniel Phillips
2005-04-27 13:56       ` Lars Marowsky-Bree
2005-04-27 20:00         ` Daniel Phillips
2005-04-27 20:20           ` Lars Marowsky-Bree
2005-04-27 22:38             ` Daniel Phillips
2005-04-28 14:57               ` Lars Marowsky-Bree
2005-04-28 20:53                 ` Daniel Phillips
2005-04-29  0:33                 ` David Lang
2005-04-29  1:49                   ` Bernd Eckenfels
2005-04-29  1:52                   ` Daniel Phillips
2005-04-29 17:13                     ` David Lang
2005-04-29 20:49                       ` Daniel Phillips
2005-05-01  3:57                       ` Theodore Ts'o
2005-05-01  4:14                         ` David Lang
2005-05-02 11:21                           ` Lars Marowsky-Bree
2005-04-28 16:25         ` David Teigland
2005-04-28 16:42           ` Lars Marowsky-Bree
2005-04-29  4:24           ` Daniel Phillips
2005-04-25 21:19   ` Andrew Morton
2005-04-26  5:46     ` David Teigland
2005-04-26  5:39   ` David Teigland
2005-04-26 18:48     ` Mark Fasheh
2005-04-26 22:34       ` Steven Dake
2005-04-27  3:32       ` David Teigland
2005-04-27 13:23       ` Lars Marowsky-Bree
2005-04-27 18:12         ` Mark Fasheh
2005-04-28 14:36           ` Lars Marowsky-Bree [this message]
2005-04-28 17:35             ` Mark Fasheh
2005-04-28 12:50         ` Stephen C. Tweedie
2005-04-25 20:52 ` Daniel Phillips

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=20050428143619.GZ21645@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --cc=teigland@redhat.com \
    --cc=wim.coekaerts@oracle.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