2016-10-03 11:33 GMT+02:00 Joe Julian <joe@xxxxxxxxxxxxxxxx>: > By default, the client reads from localhost first, if the client is also a > server, or the first to respond. This can be tuned to balance the load > better (see "gluster volume set help") but that's not necessarily more > efficient. As always, it depends on the workload. So, is no true saying that gluster aggregate bandwidth in readings. Each client will always read from 1 node. Having 3 nodes means that I can support a number of clients increased by 3. Something like an ethernet bonding, each transfer is always subject to the single port speed, but I can support twice the connections by creating a bond of 2. > Reading as you suggested is actually far less efficient. The reads would > always be coming from disk and never in any readahead cache. What I mean is to read the same file in multiple parts from multiple servers and not reading the same file part from multiple servers. _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
