[Top] [All Lists]

Re: Performance problem - reads slower than writes

To: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Subject: Re: Performance problem - reads slower than writes
From: Brian Candler <B.Candler@xxxxxxxxx>
Date: Sat, 4 Feb 2012 20:04:17 +0000
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from:to :cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=sasl; bh=soEF0Poymlqdvt5qEb4carVNLv8=; b=mDjF8IH WQU/Uwy3HcpA8nqZHDNOWdZTrzv88/lm1d/0FuLpLkPXYFeh1cf9Se9J8PzQUd/b gLaVy/JDeMnBTdyPYeIQNNA3N9uZzPFgZkgxlX6ao1MMrDOSciAj+WXq0lSFg7gW HQRFBXjQir1ofWfF3UKwCeVmp6Y9cK/nZbNQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to:cc :subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=sasl; b=DjYEOt2hVCy9TAqYOul6jZ6Y/JB62vUt+ U3JWI3FtmSrNM6R1NYe9vVE33ApmX41FHHmvPsD+tOlg/IBT760PF7iQMz3mJuaM y5XrV/23l7fr8jsA9N3YLIScOYQ8R3WloCavEK2XzZpUPvcbpWre3hUnVI62U2pd n0IQ+3rL4k=
In-reply-to: <4F2D2953.2020906@xxxxxxxxxxxxxxxxx>
References: <20120130220019.GA45782@xxxxxxxx> <20120131020508.GF9090@dastard> <20120131103126.GA46170@xxxxxxxx> <20120131145205.GA6607@xxxxxxxxxxxxx> <20120203115434.GA649@xxxxxxxx> <4F2C38BE.2010002@xxxxxxxxxxxxxxxxx> <20120203221015.GA2675@xxxxxxxx> <4F2D016C.9020406@xxxxxxxxxxxxxxxxx> <20120204112436.GA3167@xxxxxxxx> <4F2D2953.2020906@xxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Sat, Feb 04, 2012 at 06:49:23AM -0600, Stan Hoeppner wrote:
> Apparently you've read of a different GlusterFS.  The one I know of is
> for aggregating multiple storage hosts into a cloud storage resource.
> It is not designed to replace striping or concatenation of disks within
> a single host.

Sure it can. A gluster volume consists of "bricks". Each brick is served by
a glusterd process listening on a different TCP port. Those bricks can be on
the same server or on different servers.

> Even if what you describe can be done with Gluster, the performance will
> likely be significantly less than a properly setup mdraid or hardware
> raid.  Again, if it can be done, I'd test it head-to-head against RAID.

I'd expect similar throughput but higher latency. Given that I'm using low
RPM drives which already have high latency, I'm hoping the additional
latency will be insignificant.  Anyway, I'll know more once I've done the

> I've never been a fan of parity RAID, let alone double parity RAID.

I'm with you on that one.

The attractions of gluster are:
- being able to scale a volume across many nodes, transparently to
  the clients
- being able to take a whole node out of service, while clients
  automatically flip over to the other



<Prev in Thread] Current Thread [Next in Thread>