All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@google.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2 features RFC - separate journal?
Date: Thu, 04 May 2006 15:23:47 -0700	[thread overview]
Message-ID: <445A7EF3.2000701@google.com> (raw)
In-Reply-To: <445A6A61.2090009@oracle.com>

Zach Brown wrote:
>>journal.  These two things add up to a _huge_ performance boost for the
>>journal, if it can be separated.
> 
> Sure, I don't doubt the high level theory.  Does anyone have numbers to
> show it's relative effect in practice?  That'd be interesting.

I will have Ext3 numbers pretty soon.

>>It is worth remembering that not every OCFS2 user will be running it on a
>>big expensive SAN.  Probably not even the majority.
> 
> Well, that's debatable.  My only point, though, is that there are higher
> priority things that we should get to first because they affect *everyone*.

By all means, prioritize them.  Did separate journals make the list, even
if well towards the end?

> If the lack of external journals makes you sad, well, I'm sorry to hear
> that.  We certainly wouldn't turn away patches if someone got to it
> before us.

By proposing a feature that I do not also implicitly propose that Oracle
employees have to do the work.  This is a quick hack after all, I would be
happy to contribute.

>>IMHO, the separate journal on NVRAM will yield a much bigger gain and be
>>much less work besides.
> 
> So noted.  I'm curious, though.  What sort of NVRAM hardware do you have
> in mind?

For the moment, iRAM cards.  Yes I know they suck for throughput, but
there are faster SATA NVRAM cards coming down the pipe, they are still
much faster than IDE disks, and there is no seeking.

Regards,

Daniel

  parent reply	other threads:[~2006-05-04 22:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 18:35 [Ocfs2-devel] OCFS2 features RFC Mark Fasheh
2006-04-25 21:55 ` Christoph Hellwig
2006-04-25 22:24   ` Mark Fasheh
2006-04-26 16:50   ` Daniel Phillips
2006-04-26  4:11 ` Andi Kleen
2006-04-26 18:06   ` Mark Fasheh
2006-04-26 18:08     ` Andi Kleen
2006-04-26 18:34       ` Daniel Phillips
2006-04-27 20:25 ` Paul Taysom
2006-05-03 23:04 ` [Ocfs2-devel] OCFS2 features RFC - separate journal? Daniel Phillips
2006-05-04  0:29   ` Zach Brown
2006-05-04  0:46     ` Daniel Phillips
2006-05-04 20:56       ` Zach Brown
2006-05-04 20:59         ` Wim Coekaerts
2006-05-04 22:23         ` Daniel Phillips [this message]
2006-05-04 22:30           ` Mark Fasheh
2006-05-05  3:05             ` Daniel Phillips
2006-05-05 18:25               ` Mark Fasheh
2006-05-06  3:09                 ` Daniel Phillips
2006-05-05 17:12             ` Paul Taysom
2006-05-05 18:06               ` Daniel Phillips
2006-05-05 18:57               ` Sunil Mushran
2006-05-08 14:28             ` Paul Taysom
2006-05-08 17:43               ` Daniel Phillips
2006-05-08 18:00             ` Paul Taysom
2006-05-08 18:22               ` Daniel Phillips
2006-05-11 20:04 ` [Ocfs2-devel] OCFS2 features RFC Jeff Mahoney
2006-05-11 20:40   ` Paul Taysom
2006-05-11 20:55     ` Joel Becker
2006-05-11 21:16   ` Daniel Phillips
2006-05-17  1:44   ` Mark Fasheh
     [not found]     ` <446BBCF5.7040903@google.com>
     [not found]       ` <20060518024638.GY21588@ca-server1.us.oracle.com>
2006-05-19  0:35         ` Daniel Phillips
2006-05-19 15:16           ` J. Bruce Fields
2006-05-20  6:11           ` Mark Fasheh
2006-05-22 19:18             ` Daniel Phillips
2006-05-22 17:01     ` Paul Taysom

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=445A7EF3.2000701@google.com \
    --to=phillips@google.com \
    --cc=ocfs2-devel@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.