<div dir="ltr">On Thu, Sep 18, 2008 at 9:04 PM, Graeme <span dir="ltr"><<a href="mailto:graeme@sudo.ca">graeme@sudo.ca</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
<br>
Just doing some initial testing on glusterfs (1.3.10, Debian packages),<br>
and I'm somewhat underwhelmed with the performance. I setup up a test<br>
AFR and a test Unify config with two systems connected by a local,<br>
managed gigabit switch. My configs have POSIX locking, read-ahead,<br>
write-behind, and threaded i/o enabled (in that order) on the server<br>
side. I then compared bonnie output on the raw filesystems to the<br>
gluster output.<br>
</blockquote><div><br>The Debian package is slightly outdated. 1.3.12 is the latest stable
with fixes and improvements. It'd be good if you can benchmark 1.4.x as
well for it has lots of architectural changes/improvements (supposedly).<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> In particular, I thought that in an AFR config the client was supposed to<br>
automatically stripe read requests across available volumes, but the<br>
read performance doesn't seem to indicate that's happening, considering<br>
the requests it sends to itself should be able to get close to its<br>
normal ~70MB/sec rate.<br>
</blockquote><div><br>1.3.x doesn't automatically stripe read requests, unfortunately. If I'm not wrong, you'd need to add Unify over AFR.</div></div><br><br><br>KwangErn<br></div>