search for: m5dum

...eed is either super fast or 10Mb/sec. i.e. read operations take place on the local copy or the remote seemingly at random. This not the 'small files problem'. I am aware that Gluster must use network access for stat() etc. This is all about where the data comes from on a read(). If I do an m5dum on a 200Mb file it takes either half a second or 18 seconds. There is an option read-subvolume. I have tried to understand how this works from the documentation available and from the few examples on the web. I have added the option using: gluster volume set X read-subvolume Y It has no effect...