<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 11/06/2012 04:38 AM, Joe Landman
wrote:<br>
</div>
<blockquote cite="mid:509904D6.90109@scalableinformatics.com"
type="cite">On 11/06/2012 04:35 AM, Fernando Frediani (Qube)
wrote:
<br>
<blockquote type="cite">Joe,
<br>
<br>
I don't think we have to accept this as this is not acceptable
thing.
<br>
</blockquote>
<br>
I understand your unhappyness with it. But its "free" and you
sometimes have to accept what you get for "free".
<br>
<br>
</blockquote>
I slightly disagree. Yes, it's free but it's free from an
organization that's determined to take input from it's users and try
to make things better for them. Testing, filing bug reports, filing
enhancement requests, and if you have the skills offering patches:
these are the responsibility of the users in any community developed
software. "Bitching"<sup>1</sup> about deficiencies in an email
thread or blog post without having done those other things is a
waste of everyone's bandwidth.<br>
<blockquote cite="mid:509904D6.90109@scalableinformatics.com"
type="cite">
<blockquote type="cite">I have seen countless people complaining
about this problem for a
<br>
while and seems no improvements have been done. The thing about
the
<br>
ramdisk although might help, looks more a chewing gun. I have
seen
<br>
other distributed filesystems that don't suffer for the same
problem,
<br>
so why Gluster have to ?
<br>
</blockquote>
<br>
This goes to some aspect of the implementation. FUSE makes
metadata ops (and other very small IOs) problematic (as in time
consuming). There are no easy fixes for this, without engineering
a new kernel subsystem (unlikely) to incorporate Gluster, or
redesigning FUSE so this is not an issue. I am not sure either is
likely.
<br>
<br>
Red Hat may be willing to talk to you about these if you give them
money for subscriptions. They eventually relented on xfs.
<br>
<br>
</blockquote>
Besides that, a metadata op is small. Add network overhead and it's
much slower than local filesystems could ever be. If you want rid of
that problem, use IB rdma. <br>
<br>
I'll grant that the documentation says that rdma is not supported.
What I've come to understand that meaning is that it's just as
unsupported as any previous version was. After the acquisition,
untested features were deemed "technology preview" and were
"unsupported" as that. Once they've gone through RH QA they can be
removed from that status. Apparently rdma wasn't high enough on the
priority list to be tested before the last RHS release, thus that
status remains. I don't think it works any less than it did with
3.2. I've seen various success with IB and wonder if it's hardware
related.<br>
<br>
<sup>1 </sup>I'm not targeting this email thread with this word.
For the most part this seems to be a productive and thoughtful
discussion. It's just a general denouncement of this behavior across
the internet for all community developed software.<br>
</body>
</html>