Hello,
you can try tuning your TCP settings to be more aggressives (both on 1 client and all gluster bricks) in /etc/systctl.conf:
net.core.rmem_max=67108864
net.core.wmem_max=67108864
# increase Linux autotuning TCP buffer limit to 32MB
net.ipv4.tcp_rmem="4096 87380 33554432"
net.ipv4.tcp_wmem="4096 65536 33554432"
# increase the length of the processor input queue
net.core.netdev_max_backlog=30000
# recommended default congestion control is htcp
net.ipv4.tcp_congestion_control=htcp
2015-07-18 22:11 GMT+02:00 Roman <romeo.r@xxxxxxxxx>:
But when I'm inside of VM, I'm getting 50-53 MB/s for replica and 120 MB for distributed volumes...whats the logic? that slow write speed directly to mounted gfs volume slows down backup and restore process of VMs by VE.--2015-07-18 22:47 GMT+03:00 Roman <romeo.r@xxxxxxxxx>:Hi,Looked a lot from forums, but didn't find much..So I've got glusterfs 3.6.41 Gbps networkreplicate and distributed volumesso when i read from any of them, I get maxed-out network performance (around 80-120 MB/sec)If i write to distributed volume, I get 16 MB/secIf i write to replicated volume, I get around half of it (which is logical) 8-10MB/seci use XFS (with all set recommended options) and EXT4 for gluster. no difference.Disks are in HW RAID5 for Distributed volume and RAID0 for Replicated volumevolume options:performance.write-behind: offserver.allow-insecure: oncluster.server-quorum-type: servercluster.quorum-type: autonetwork.remote-dio: enablecluster.eager-lock: enableperformance.stat-prefetch: offperformance.io-cache: offperformance.read-ahead: offperformance.quick-read: offAm I missing something?--Best regards,
Roman.Best regards,
Roman.
_______________________________________________
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
