On Sat, 2015-02-07 at 20:41 +0100, Peter Prusi wrote: > Hello, > > I'm new to glusterfs and I dont understand 'the > performance.write-behind-window-size' option. I'm using glusterfs 3.5.2 > and setup a volume over two nodes connected over 1 GbE. > Actually the write performance is about 58 Mb/s. This means glusterfs > writes the data simultaneous on both nodes. I'm trying to increase the > write speed and I thought this option would cache the data > on one node and then distribute to the other. So i could double the > speed. I played around with this option, but it has no effect to the > write speed. Write-behind does three jobs with respect to a write-request. One among them is, it will lie to application, which issued the write-request about the completion of write and then will perform this write operation in background. Basically, For a single inode, it will lie to the application until current size of the total lied request which are not fulfilled on nodes becomes equal to the window size. This size is configurable through performance.write-behind-window-size . > What am I doing wrong or > is there another tweak to increase the write > speed ? I'm not familiar with write performance tweaks. Some one more familiar with this can comment on this. Regards Rafi KC > > Thank you > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
