[Gluster-users] Read performances low compared to write (second try)

Olivier JAVAUX olivier.javaux at orange.fr
Fri Jul 10 08:56:28 UTC 2015

> Can you disable gluster's read-ahead translator and try again?
I am new to glusterfs.
To disable read-ahead xlator, I do:

gluster volume set <vol_name> performance.read-ahead off


> Additionally o/p of gluster volume info will be useful.

# gluster volume info DFS

Volume Name: DFS
Type: Distributed-Replicate
Volume ID: 2cde4f9e-73c4-4555-a91c-d63873453b2a
Status: Started
Number of Bricks: 6 x 2 = 12
Transport-type: tcp
Brick1: DRS-MM-ADM-01-CLU:/glusterfs/data/brick
Brick2: DRS-MM-DWH-01-CLU:/glusterfs/data/brick
Brick3: DRS-MM-PRO-01-CLU:/glusterfs/data/brick
Brick4: DRS-MM-PRO-02-CLU:/glusterfs/data/brick
Brick5: DRS-MM-PRO-03-CLU:/glusterfs/data/brick
Brick6: DRS-MM-PRO-04-CLU:/glusterfs/data/brick
Brick7: DRS-MM-PRO-05-CLU:/glusterfs/data/brick
Brick8: DRS-MM-PRO-06-CLU:/glusterfs/data/brick
Brick9: DRS-MM-PRO-07-CLU:/glusterfs/data/brick
Brick10: DRS-MM-PRO-08-CLU:/glusterfs/data/brick
Brick11: DRS-MM-PRO-09-CLU:/glusterfs/data/brick
Brick12: DRS-MM-PRO-10-CLU:/glusterfs/data/brick
Options Reconfigured:
performance.read-ahead: on
performance.read-ahead-page-count: 16
performance.io-thread-count: 32
performance.cache-size: 1GB

Thanks for your help

Best regards,


More information about the Gluster-users mailing list