On Sun, Jul 17, 2011 at 10:19:00PM -0500, Ken Randall wrote: > (The no such file or directory part is expected since some of the image > references don't exist.) Wild guess on that: Gluster may work harder at files it doesn't find than files it finds. It's going to look on one side or the other of the replicated file at first, and if it finds the file deliver it. But if it doesn't find the file, wouldn't it then check the other side of the replicated storage to make sure this wasn't a replication error? Might be interesting to run a version of the test where all the images referenced do exist, to see if it's the missing files that are driving up the CPU cycles. Whit
