<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 15 March 2016 at 11:54, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Mar 14, 2016 at 05:43:05PM +0530, M S Vishwanath Bhat wrote:<br>
> On 14 March 2016 at 14:29, Raghavendra Talur <<a href="mailto:rtalur@redhat.com">rtalur@redhat.com</a>> wrote:<br>
><br>
> ><br>
> ><br>
> > On Mon, Mar 14, 2016 at 8:40 AM, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br>
> ><br>
> >> Hey Vijay,<br>
> >><br>
> >> Awesome work on the tests!<br>
> >><br>
> > +1<br>
> ><br>
> ><br>
> ><br>
> >><br>
> >> Could you please list down the tests you run for releases? This would<br>
> >> help the other release-maintainers could run them as well. We could<br>
> >> also try automating these tests, so that it becomes even easier.<br>
> ><br>
> ><br>
> > +1, I will add it to the vagrant setup I have on gluster repo.<br>
> ><br>
><br>
> If we identify all the release tests to be done, I can write distaf test<br>
> cases for the same. We can possibly run them in the vagrant setup as well.<br>
<br>
Running these distaf tests in a Vagrant environment should be possible<br>
in the CentOS CI. James Shubin has some tests he runs like that, and can<br>
point you to them for inspiration (Oh-my-vagrant?).<br></blockquote><div><br></div><div>If it is in CentOS CI, then why do we need vagrant? I'm not sure how vagrant would make things more simple.</div><div><br></div><div>We can use duffy to provision the machines, we can use gdeploy to install glusterfs and use distaf to run the tests. In the nightly job I created, it is using the same (minus the gdeploy, they don't have gdeploy in pypi yet).</div><div><br></div><div>Best Regards,</div><div>Vishwanath</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Niels<br>
<br>
<br>
><br>
> Best Regards,<br>
> Vishwanath<br>
><br>
><br>
> ><br>
> >><br>
> >> ~kaushal<br>
> >><br>
> >> On Sun, Mar 13, 2016 at 10:50 PM, Vijay Bellur <<a href="mailto:vbellur@redhat.com">vbellur@redhat.com</a>><br>
> >> wrote:<br>
> >> > Hey All,<br>
> >> ><br>
> >> > I have been running tests with the latest HEAD of release-3.7 on a 2x2<br>
> >> > distributed replicated volume. Here are some updates:<br>
> >> ><br>
> >> > - Write Performance has seen an improvement as seen by running<br>
> >> perf-test.sh<br>
> >> > [1]<br>
> >> ><br>
> >> ><br>
> >> > v3.7.9 with FUSE client<br>
> >> ><br>
> >> > Testname Time<br>
> >> > emptyfiles_create 961.83<br>
> >> > emptyfiles_delete 600.08<br>
> >> > smallfiles_create 1508.38<br>
> >> > smallfiles_rewrite 1325.60<br>
> >> > smallfiles_read 598.50<br>
> >> > smallfiles_reread 384.65<br>
> >> > smallfiles_delete 623.66<br>
> >> > largefile_create 18.33<br>
> >> > largefile_rewrite 19.17<br>
> >> > largefile_read 11.44<br>
> >> > largefile_reread 0.31<br>
> >> > largefile_delete 0.66<br>
> >> > directory_crawl_create 981.21<br>
> >> > directory_crawl 30.64<br>
> >> > directory_recrawl 28.01<br>
> >> > metadata_modify 1117.92<br>
> >> > directory_crawl_delete 423.08<br>
> >> ><br>
> >> > v3.7.8 with FUSE client<br>
> >> ><br>
> >> > Testname Time<br>
> >> > emptyfiles_create 953.87<br>
> >> > emptyfiles_delete 577.46<br>
> >> > smallfiles_create 1837.33<br>
> >> > smallfiles_rewrite 2349.37<br>
> >> > smallfiles_read 604.22<br>
> >> > smallfiles_reread 394.48<br>
> >> > smallfiles_delete 629.74<br>
> >> > largefile_create 73.86<br>
> >> > largefile_rewrite 76.23<br>
> >> > largefile_read 11.36<br>
> >> > largefile_reread 0.31<br>
> >> > largefile_delete 0.65<br>
> >> > directory_crawl_create 985.16<br>
> >> > directory_crawl 31.10<br>
> >> > directory_recrawl 26.94<br>
> >> > metadata_modify 1422.60<br>
> >> > directory_crawl_delete 382.57<br>
> >> ><br>
> >> > Hopefully this addresses the write performance drop we observed with<br>
> >> 3.7.8.<br>
> >> ><br>
> >> > - Regular file system test tools like iozone, dbench etc. are running<br>
> >> fine<br>
> >> > with the fuse client.<br>
> >> ><br>
> >> > - Rolling upgrade from 3.7.8 to the latest release-3.7 HEAD worked fine<br>
> >> with<br>
> >> > I/O happening from a fuse client.<br>
> >> ><br>
> >> > - There is a memory leak in FUSE client that I observed while running<br>
> >> > perf-test.sh. A statedump revealed that there was a ref leak on several<br>
> >> > inodes. I have sent a possible patch [2] which addressed problems in my<br>
> >> test<br>
> >> > setup. This does need careful review and more testing. Given the memory<br>
> >> > leaks we have been observing with fuse, I feel that it would be good to<br>
> >> > review mount/fuse for possible leaks and run more tests before releasing<br>
> >> > 3.7.9. I am looking at pushing out tagging by 2-3 days to mid week to<br>
> >> > accomplish this. Niels, Raghavendra - can you provide additional help<br>
> >> with<br>
> >> > reviewing here?<br>
> >> ><br>
> >> > - Tiering has seen a lot of patches in 3.7.9. Dan, Nithya - can you<br>
> >> please<br>
> >> > assist in preparation of release notes by summarizing the changes and<br>
> >> > providing inputs on the general readiness of tiering?<br>
> >> ><br>
> >> > Thanks,<br>
> >> > Vijay<br>
> >> ><br>
> >> > [1] <a href="https://github.com/avati/perf-test/blob/master/perf-test.sh" rel="noreferrer" target="_blank">https://github.com/avati/perf-test/blob/master/perf-test.sh</a><br>
> >> ><br>
> >> > [2] <a href="http://review.gluster.org/#/c/13689/" rel="noreferrer" target="_blank">http://review.gluster.org/#/c/13689/</a><br>
> >> ><br>
> >> ><br>
> >> > _______________________________________________<br>
> >> > Gluster-devel mailing list<br>
> >> > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> >> > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> >> _______________________________________________<br>
> >> Gluster-devel mailing list<br>
> >> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> >> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> >><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Gluster-devel mailing list<br>
> > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> ><br>
<br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
</blockquote></div><br></div></div>