Hi I have 2 gluster server (backup1 , backup2) connected with 10Gbit link glusterfs version 10.3-1 server and client
Each server is with 44T disk raid 6 with 1 partition used for the brick /dev/VG_BT_BRICK1/LV_BT_BRICK1 [ 43.66 TiB] /dev/mapper/VG_BT_BRICK1-LV_BT_BRICK1 on /mnt/glusterfs type xfs (rw,noatime,nouuid,attr2,inode64,sunit=256,swidth=1536,noquota) I create a replica volume named backup Volume Name: backup Type: Replicate Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: backup-1:/mnt/glusterfs/brick1 Brick2: backup-2:/mnt/glusterfs/brick1 Options Reconfigured: cluster.granular-entry-heal: on storage.fips-mode-rchecksum: on transport.address-family: inet nfs.disable: on performance.client-io-threads: off cluster.enable-shared-storage: enable The volume backup is mounted with gluster client on /mnt/share backup-1:/backup on /mnt/share type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) Test with smallfile utility XFS with filesystem xfs on /mnt/glusterfs total threads = 8 total files = 800 100.00% of requested files processed, warning threshold is 70.00% elapsed time = 0.009 files/sec = 120927.642211 GLUSTERFS CLIENT with glusterfs on /mnt/share total threads = 8 total files = 800 100.00% of requested files processed, warning threshold is 70.00% elapsed time = 3.014 files/sec = 284.975861 How is it possible to increase the performance in glusterfs volume ? How is best practice of brick size and replica management ? Is better 1 big brick per server or more small bricks distributed ? Many Thanks
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
