won't read at those speeds.
Thanks!
-Mic
Hiren Joshi wrote:
-Original Message-
From: Stephan von Krawczynski [mailto:sk...@ithnet.com]
Sent: 09 July 2009 13:50
To: Hiren Joshi
Cc: Liam Slusser; gluster-users@gluster.org
Subject: Re: [Gluster-users] GlusterFS Preformance
On T
> -Original Message-
> From: Stephan von Krawczynski [mailto:sk...@ithnet.com]
> Sent: 09 July 2009 13:50
> To: Hiren Joshi
> Cc: Liam Slusser; gluster-users@gluster.org
> Subject: Re: [Gluster-users] GlusterFS Preformance
>
> On Thu, 9 Jul 2009 09:33:59 +010
On Thu, 9 Jul 2009 09:33:59 +0100
"Hiren Joshi" wrote:
>
>
> > -Original Message-
> > From: Stephan von Krawczynski [mailto:sk...@ithnet.com]
> > Sent: 09 July 2009 09:08
> > To: Liam Slusser
> > Cc: Hiren Joshi; gluster-users@gluster.
> -Original Message-
> From: Stephan von Krawczynski [mailto:sk...@ithnet.com]
> Sent: 09 July 2009 09:08
> To: Liam Slusser
> Cc: Hiren Joshi; gluster-users@gluster.org
> Subject: Re: [Gluster-users] GlusterFS Preformance
>
> On Wed, 8 Jul 2009 10:05:58 -07
On Wed, 8 Jul 2009 10:05:58 -0700
Liam Slusser wrote:
> You have to remember that when you are writing with NFS you're writing to
> one node, where as your gluster setup below is copying the same data to two
> nodes; so you're doubling the bandwidth. Dont expect nfs like performance
> on writin
>
> I ran a basic test by writing 1G to an NFS server and this gluster pair:
> [r...@glust1 ~]# time dd if=/dev/zero of=/mnt/glust2_nfs/nfs_test
> bs=65536 count=15625
> 15625+0 records in
> 15625+0 records out
> 102400 bytes (1.0 GB) copied, 1718.16 seconds, 596 kB/s
>
> real 28m38.278s
> u
You have to remember that when you are writing with NFS you're writing to
one node, where as your gluster setup below is copying the same data to two
nodes; so you're doubling the bandwidth. Dont expect nfs like performance
on writing with multiple storage bricks. However read performance should
