Gluster users - May 2010 - Performance questions/tweaks on Gluster

I've now got Gluster 3.04 up and running on my servers. 

Setup: 

gluster1 - back end file server 
gluster2 - ditto. Redundant. These are setup with the --raid 1 option 
app1 - my app server mounts /data/export on /home 
app2 - ditto 

The appropriate conf files are attached. 

My simple test involves reading an input file and writing it to the Gluster home
versus local /tmp.

Writing is 65x-ish slower. Reading is 28x-ish slower. Now, obviously,
there's some overhead with regards to the Gluster system, and while the
overall numbers themselves aren't bad in the real world, I'm wondering
what, if any, performance tweaks I could be using to help this out.

The app servers are far more read-heavy than write-heavy. Writing will be done
in small chunks appending to files (audit logging, uploading images, writing out
temp files from the application).

glusterTest output: 

Writing 4879 lines to /home/output 
11.4823799133 
Writing 4879 lines to /tmp/output 
0.173233985901 
Reading /home/output 
Read 43911 lines in 0.757484197617 seconds. 
Reading /tmp/output 
Read 43911 lines in 0.0274169445038 seconds. 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gluster1.txt
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20100521/8bd8e527/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gluster2.txt
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20100521/8bd8e527/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: client.txt
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20100521/8bd8e527/attachment-0002.txt>