<br><br><div class="gmail_quote">On Mon, Jan 12, 2009 at 6:57 PM, Keith Freedman <span dir="ltr"><<a href="mailto:freedman@freeformit.com">freedman@freeformit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
check back to some of the previous messages in this list about performance.</blockquote><div>Ok , I will check too .<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;">
<br>
also, which version of Gluster you use makes a difference.</blockquote><div>I am using <br><br>GlusterFS version: glusterfs 1.4.0rc7 <br><br>FUSE Version :fuse-2.7.3glfs10<br><br>My Client and Server machine RAM size : 384MB(128MB+256MB)
<br><br>This the volume file I am using for benchmarking.<br><br><br>### file: client-volume.vol.sample<br><br>### Add client feature and attach to remote subvolume<br><br>volume client<br> type protocol/client<br> option transport-type tcp<br>
option remote-host 192.168.1.167 <br> option remote-subvolume brick <br>end-volume<br><br>### Add readahead feature<br>volume readahead<br> type performance/read-ahead<br> option page-size 128kB <br> option page-count 4 <br>
subvolumes client<br>end-volume<br><br>### Add IO-Cache feature<br>volume iocache<br> type performance/io-cache<br> subvolumes readahead <br> #option page-size 1MB # 128KB is default<br> option cache-size 300MB # 32MB is default<br>
option cache-timeout 5 # 1second is default <br> #option priority *.html:2,*:1 # default is *:0<br>end-volume<br><br>### Add writeback feature<br>volume writeback<br> type performance/write-behind<br> option aggregate-size 128KB<br>
option window-size 2MB<br> option flush-behind on<br> subvolumes iocache <br>end-volume<br><br><br><br> <br>### file: server-volume.vol.sample<br><br>volume brick<br> type storage/posix <br> option directory /bench <br>
end-volume<br><br>volume plocks<br> type features/posix-locks<br> subvolumes brick<br> # option mandatory on<br>end-volume<br><br>volume iot<br> type performance/io-threads<br> subvolumes plocks <br> option thread-count 8 <br>
# option cache-size 4MB <br>end-volume<br><br>volume server<br> type protocol/server<br> subvolumes iot brick<br> option transport-type tcp<br> option auth.addr.brick.allow 192.168. *<br> option auth.addr.iot.allow 192.168.*<br>
end-volume<br><br>I am using io-threads on server side only .can I use same on client side? It will increase the performance ? How to tune translator parameters? I mean I am using page-size in iocache 128K how to know which parameter will performs better ? <br>
<br>Next I am aiming to set up more server and client to get the performance gain .<br><br>we are aiming at solving the problems of Millions/Billions of small files
inside a single directory, Though, the files are not saved as files
inside each directory, they will be saved inside a db file .We are using MySQL . How to achive this for testing perpose? As know I don't have enough skill to do same . Please give me some guide line to achive this kind of set up . I am not able to get how to export db file over GlusterFS. what is your Idea?<br>
<br><br> <br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
As for smaller block sizes being a performance issue, I think mostly fuse is the problem with small block sizes.<br>
I think 4K is what fuse' block size is? SO I'm thinking that should be ok for testing.</blockquote><div><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
I also believe gluster 2.0 is much faster with smaller files than 1.3, so you should get better results with 2.0</blockquote><div><br>I saw last week one thread about 2.0 .But I am not able to find where I have to download 2.0? Please give me the download URL of 2.0 . <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
if you benchmarked with 1.3, please try again with 2.0 and let us know your results.</blockquote><div> Sure , I will send 2.0 benchmark also .<br><br>Thanks for your time <br><br>Thanks<br>L.Mohan<br> </div></div><br>