Vijay:
I just tried that and the results using this command:
# for i in `seq -w 1 4`; do dd if=/dev/zero of=10Gfile$1 bs=1024k count=10240; done
is about 1/4th the write performance of a distributed volume.
(I'm currently testing with a 64 GB RAM drive on each of my four compute nodes that are then tied together using GlusterFS).
With a distributed volume, and with direct-io-mode=enable, at best, I can execute that same task at around 2 GB/s. (The host system could execute that task at around 2.8 GB/s to /dev/shm.)
With a dispersed volume with 1 brick for redundancy, it drops to around 500 MB/s at best.
Is there no other way to be get the kind of performance that stripping should theorectically provide?
Thank you.
Sincerely,
Ewen
From: Vijay Bellur <vbellur@xxxxxxxxxx>
Sent: August 20, 2019 7:50 PM To: Ewen Chan <alpha754293@xxxxxxxxxxx> Cc: gluster-users@xxxxxxxxxxx <gluster-users@xxxxxxxxxxx> Subject: Re: Can I create a distributed dispersed volume with RAM drives? On Tue, Aug 20, 2019 at 4:47 PM Ewen Chan <alpha754293@xxxxxxxxxxx> wrote:
Creating stripe volumes has been deprecated in recent releases. You can create a dispersed volume using the following syntax:
# gluster volume create [disperse [<count>]] [redundancy <count>] <brick-list>
HTH,
Vijay
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users